Published package metadata cannot be changed without shipping another version, so this has to land before 0.1.0 goes out, not after. - repository/homepage/bugs were all missing: the npm page would have rendered with no link back to the source at all. repository names the GitHub mirror deliberately — npm tooling and the --provenance attestation are keyed to the repo the workflow builds in; the canonical repository is stated in the README instead. - README is the npm page body. Its Quick Start opened with `cd mcp-server && npm install`, which is the from-a-clone path — the one instruction that cannot work for somebody who just installed the package. `npx fleet-memory-mcp` first, clone path kept below it, and a line saying this package is the client half and does not start a store. - LICENSE was not in the tarball. MIT text now ships with the artifact, Vectorize AI copyright intact. - engines and an explicit files list, so the tarball contents are stated rather than inferred.
21 lines
1 KiB
Text
21 lines
1 KiB
Text
MIT License
|
|
|
|
Copyright (c) 2025 Vectorize AI, Inc.
|
|
|
|
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
of this software and associated documentation files (the "Software"), to deal
|
|
in the Software without restriction, including without limitation the rights
|
|
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
copies of the Software, and to permit persons to whom the Software is
|
|
furnished to do so, subject to the following conditions:
|
|
|
|
The above copyright notice and this permission notice shall be included in all
|
|
copies or substantial portions of the Software.
|
|
|
|
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
SOFTWARE.
|