← Home

@getmikk/mcp-server

npm Repository Homepage
11
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ansh_dhanani

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:zod AI (phantom-deps): Used indirectly via config/build, common false positive. ai
phantom-deps phantom-dep:@getmikk/core AI (phantom-deps): Same-org sibling package, expected phantom flag. ai
phantom-deps phantom-dep:@getmikk/ai-context AI (phantom-deps): Same-org sibling package, expected phantom flag. ai
phantom-deps phantom-dep:@getmikk/intent-engine AI (phantom-deps): Same-org sibling package, expected phantom flag. ai
phantom-deps phantom-dep:better-sqlite3 AI (phantom-deps): Native binding referenced via config, not direct import. ai
phantom-deps phantom-dep:web-tree-sitter AI (phantom-deps): Referenced via config, not direct import. ai
phantom-deps phantom-dep:@xenova/transformers AI (phantom-deps): Referenced via config, not direct import. ai
phantom-deps phantom-dep:@modelcontextprotocol/sdk AI (phantom-deps): Well-known MCP SDK dependency, expected phantom flag. ai

Versions (showing 11 of 11)

Version Deps Published
2.0.0 8 / 3
1.10.1 8 / 3
1.10.0 8 / 3
1.9.2 8 / 3
1.9.1 4 / 7
1.9.0 4 / 7
1.8.1 2 / 7
1.8.0 2 / 7
1.7.0 2 / 7
1.6.0 2 / 7
1.5.1 2 / 7

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.