@mongosh/service-provider-node-driver
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:socks | AI (phantom-deps): socks is a declared runtime dep used transitively by the MongoDB driver; phantom-dep heuristic fires but it's a legitimate dependency. | ai | |
| phantom-deps | phantom-dep:gcp-metadata | AI (phantom-deps): gcp-metadata is a declared runtime dep for GCP auth support; indirect usage is expected in this service provider. | ai | |
| phantom-deps | phantom-dep:@mongodb-js/oidc-plugin | AI (phantom-deps): Declared dep for OIDC auth; loaded by convention/config rather than direct import is normal for plugin-style auth providers. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/credential-providers | AI (phantom-deps): Framework-scoped AWS SDK dep; loaded by convention for AWS auth support, consistent with package purpose. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.0.11 | 13 / 7 | |
| 5.0.0 | 13 / 7 | |
| 3.18.0 | 12 / 7 | |
| 3.17.7 | 12 / 7 | |
| 3.17.5 | 12 / 7 | |
| 3.17.4 | 12 / 7 |
v5.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.