@mongodb-js/device-id
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): MongoDB-js monorepo tooling package; templated naming and sparse README are expected for internal scoped packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.4.13 | 0 / 17 | |
| 0.4.11 | 0 / 17 | |
| 0.4.10 | 0 / 17 | |
| 0.4.9 | 0 / 17 | |
| 0.4.8 | 0 / 17 | |
| 0.4.7 | 0 / 17 | |
| 0.4.6 | 0 / 17 | |
| 0.4.5 | 0 / 17 | |
| 0.4.4 | 0 / 17 | |
| 0.4.3 | 0 / 17 | |
| 0.4.0 | 0 / 17 | |
| 0.3.3 | 0 / 17 | |
| 0.3.2 | 0 / 17 | |
| 0.3.1 | 0 / 17 | |
| 0.3.0 | 0 / 17 | |
| 0.2.1 | 0 / 17 | |
| 0.2.0 | 0 / 17 |
v0.4.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.