← Home

@notionhq/notion-mcp-server

npm Repository Homepage
5
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

michaelfromyegatnotionjitlrhart_notionalma-notionnishadagrawalkiran-notionmlafontantloliverijfong-notionsharc.notionparulbawejanickzubereling8welegancristina-notionjclem-ntnbenkraft-notionksinder-notionquan-notionhallie.notion

Keywords

notionapimcpserver

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): Fires on console.log printing local bind address 0.0.0.0; not an outbound network request. Stable false positive for this package. ai
phantom-deps phantom-dep:zod AI (phantom-deps): zod is a declared runtime dependency; phantom-dep heuristic misfires on config-referenced deps. ai
phantom-deps phantom-dep:which AI (phantom-deps): which is a declared runtime dependency; phantom-dep heuristic misfires on config-referenced deps. ai
phantom-deps phantom-dep:yargs AI (phantom-deps): yargs is a declared runtime dependency; phantom-dep heuristic misfires on config-referenced deps. ai
phantom-deps phantom-dep:node-fetch AI (phantom-deps): node-fetch is a declared runtime dependency; phantom-dep heuristic misfires on config-referenced deps. ai

Versions (showing 5 of 5)

Version Deps Published
2.2.1 12 / 14
2.2.0 12 / 14
2.1.0 12 / 14
2.0.0 12 / 14
1.9.1 12 / 14

v2.2.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.

v2.2.0

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.

v2.1.0

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.

v2.0.0

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.9.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.