@mongodb-js/devtools-proxy-support
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 org package with templated naming convention; mass-production signal is expected for a large org monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Established MongoDB package; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:system-ca | AI (dependencies): system-ca is a standard OS certificate store reader; expected dependency for a proxy/TLS utility. | ai | |
| dependencies | unvetted-dep:@mongodb-js/socksv5 | AI (dependencies): First-party MongoDB SOCKS5 dep; expected for this proxy-support package. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.7.18 | 11 / 20 | |
| 0.7.17 | 11 / 20 | |
| 0.7.16 | 11 / 20 | |
| 0.7.15 | 11 / 20 | |
| 0.7.14 | 11 / 20 | |
| 0.7.13 | 11 / 20 | |
| 0.7.12 | 11 / 20 | |
| 0.7.11 | 11 / 20 | |
| 0.7.10 | 11 / 20 | |
| 0.7.9 | 11 / 20 | |
| 0.7.8 | 11 / 20 | |
| 0.7.6 | 11 / 20 | |
| 0.7.5 | 11 / 20 | |
| 0.7.4 | 11 / 20 | |
| 0.7.3 | 11 / 20 | |
| 0.7.2 | 11 / 20 | |
| 0.7.1 | 11 / 20 | |
| 0.6.0 | 11 / 20 | |
| 0.5.5 | 11 / 20 | |
| 0.5.4 | 11 / 20 | |
| 0.5.3 | 11 / 20 | |
| 0.5.2 | 11 / 20 | |
| 0.5.1 | 11 / 20 | |
| 0.5.0 | 11 / 20 | |
| 0.4.4 | 11 / 20 | |
| 0.4.3 | 11 / 20 | |
| 0.4.2 | 11 / 20 | |
| 0.4.1 | 11 / 20 | |
| 0.4.0 | 11 / 20 | |
| 0.3.10 | 11 / 20 | |
| 0.3.9 | 11 / 20 | |
| 0.3.8 | 11 / 20 | |
| 0.3.7 | 11 / 20 | |
| 0.3.6 | 11 / 20 | |
| 0.3.5 | 11 / 20 | |
| 0.3.4 | 11 / 20 | |
| 0.3.3 | 10 / 20 | |
| 0.3.2 | 10 / 20 | |
| 0.3.1 | 6 / 20 | |
| 0.3.0 | 6 / 20 | |
| 0.2.0 | 5 / 20 |
v0.7.18
2 findingsThis version was published by a different npm account than previous versions on unknown date. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
2 findings[Accepted risk] Package 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.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.