@mintlify/mcp
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 @mintlify package; Levenshtein match to 'yup' is a false positive with no impersonation intent. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): js-yaml is a direct dep used via config files; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:posthog-node | AI (phantom-deps): posthog-node is a direct dep used via config files; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:@types/unist | AI (phantom-deps): Framework-scoped type package; phantom-dep heuristic correctly notes it's loaded by convention. | ai |
Versions (showing 8 of 108)
| Version | Deps | Published |
|---|---|---|
| 1.1.116 | 16 / 7 | |
| 1.1.115 | 16 / 7 | |
| 1.1.114 | 16 / 7 | |
| 1.1.113 | 16 / 7 | |
| 1.1.112 | 16 / 7 | |
| 1.1.111 | 16 / 7 | |
| 1.1.110 | 16 / 7 | |
| 1.1.109 | 16 / 7 |
v1.1.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.