@elephance/mcp
MCP server for elephance local vector memory and schema retrieval
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped MCP server package; Levenshtein match to 'yup' is a false positive with no semantic similarity. | ai | |
| phantom-deps | phantom-dep:openai | AI (phantom-deps): openai is declared as a runtime dep and referenced in config; phantom-dep heuristic misfires here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 5 / 0 | |
| 0.3.0 | 5 / 0 | |
| 0.2.0 | 5 / 0 | |
| 0.1.1 | 4 / 0 | |
| 0.1.0 | 3 / 0 |
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.