@mongodb-js/ts-autocomplete
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
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.5.13 | 3 / 16 | |
| 0.5.12 | 3 / 16 | |
| 0.5.11 | 3 / 16 | |
| 0.5.10 | 3 / 16 | |
| 0.5.9 | 3 / 16 | |
| 0.5.8 | 3 / 16 | |
| 0.5.7 | 3 / 16 | |
| 0.5.6 | 3 / 16 | |
| 0.5.5 | 3 / 16 | |
| 0.5.4 | 3 / 16 | |
| 0.5.3 | 3 / 16 | |
| 0.5.0 | 3 / 16 | |
| 0.4.8 | 3 / 16 | |
| 0.4.7 | 3 / 16 | |
| 0.4.6 | 3 / 16 | |
| 0.4.5 | 3 / 16 | |
| 0.4.4 | 3 / 16 | |
| 0.4.3 | 3 / 16 | |
| 0.4.2 | 3 / 16 | |
| 0.4.1 | 3 / 16 | |
| 0.4.0 | 3 / 15 | |
| 0.3.3 | 3 / 15 | |
| 0.3.2 | 3 / 15 | |
| 0.3.1 | 3 / 15 | |
| 0.3.0 | 0 / 18 | |
| 0.2.1 | 0 / 17 | |
| 0.2.0 | 0 / 17 |
v0.5.13
2 findingsThis version was published by a different npm account than previous versions on 2026-07-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
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.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.