@mongodb-js/oidc-mock-provider
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): mcasimir_mdb appears to be a renamed account of mcasimir within MongoDB org; not a third-party takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added for same person (account rename); not a hostile removal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate MongoDB test utility in the mongodb-js org; mass-production signal reflects org-wide package templating, not spam. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.13.13 | 1 / 17 | |
| 0.13.12 | 1 / 17 | |
| 0.13.11 | 1 / 17 | |
| 0.13.10 | 1 / 17 | |
| 0.13.9 | 1 / 17 | |
| 0.13.8 | 1 / 17 | |
| 0.13.7 | 1 / 17 | |
| 0.13.6 | 1 / 17 | |
| 0.13.5 | 1 / 17 | |
| 0.13.4 | 1 / 17 | |
| 0.13.3 | 1 / 17 | |
| 0.13.0 | 1 / 17 | |
| 0.12.0 | 1 / 17 | |
| 0.11.5 | 1 / 17 | |
| 0.11.4 | 1 / 17 | |
| 0.11.3 | 1 / 17 | |
| 0.11.2 | 1 / 17 | |
| 0.11.1 | 1 / 17 | |
| 0.11.0 | 1 / 17 | |
| 0.10.3 | 1 / 17 | |
| 0.10.2 | 1 / 17 | |
| 0.10.1 | 1 / 17 | |
| 0.10.0 | 1 / 17 | |
| 0.9.3 | 1 / 17 | |
| 0.9.2 | 1 / 17 | |
| 0.9.1 | 1 / 17 |
v0.13.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gribnoysup) than the most recent previously approved version (devtoolsbot) on 2026-06-30, but gribnoysup is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.