@mongodb-js/mongodb-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
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): New account is trusted internal publisher w/ strong approval history. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org-wide publisher migration, not a takeover. | ai | |
| dependencies | unvetted-dep:@mongosh/shell-api | AI (dependencies): First-party MongoDB/mongosh package; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:mongodb-schema | AI (dependencies): First-party MongoDB package; stable dependency for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is from bundling .d.ts type files as string data; expected for this package's extract-types build step. | ai | |
| source-diff | obfuscated-file:dist/types/autocomplete-types.js | AI (source-diff): File bundles TypeScript .d.ts contents as string literals for autocomplete; long lines are embedded type definitions, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/types/autocomplete-types.js | AI (source-diff): Network/exec patterns are inside embedded string literals (type definitions), not executable code paths. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate MongoDB Inc package in the mongodb-js org; mass-production signal is a false positive for this org's monorepo pattern. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop explained by extraction of logic into @mongodb-js/ts-autocomplete dependency; not a stub/redirect. | ai | |
| provenance | no-provenance | AI (provenance): MongoDB devtoolsbot consistently publishes without provenance; stable pattern across 50 approved packages. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.8.2 | 7 / 20 | |
| 0.8.1 | 7 / 20 | |
| 0.8.0 | 7 / 20 | |
| 0.7.3 | 7 / 20 | |
| 0.7.2 | 7 / 20 | |
| 0.7.1 | 7 / 20 | |
| 0.6.17 | 7 / 20 | |
| 0.6.16 | 7 / 20 | |
| 0.6.15 | 7 / 20 | |
| 0.6.14 | 7 / 20 | |
| 0.6.13 | 7 / 20 | |
| 0.6.12 | 7 / 20 | |
| 0.6.10 | 7 / 20 | |
| 0.6.9 | 7 / 20 | |
| 0.6.8 | 7 / 20 | |
| 0.6.7 | 7 / 20 | |
| 0.6.6 | 7 / 20 | |
| 0.6.5 | 7 / 20 | |
| 0.6.4 | 7 / 20 | |
| 0.6.3 | 7 / 20 | |
| 0.6.2 | 7 / 20 | |
| 0.6.1 | 7 / 20 | |
| 0.5.0 | 7 / 20 | |
| 0.4.10 | 7 / 20 | |
| 0.4.9 | 7 / 20 | |
| 0.4.8 | 7 / 20 | |
| 0.4.7 | 7 / 20 | |
| 0.4.6 | 7 / 20 | |
| 0.4.5 | 7 / 20 | |
| 0.4.4 | 7 / 20 | |
| 0.4.3 | 7 / 20 | |
| 0.4.1 | 7 / 20 | |
| 0.4.0 | 7 / 20 | |
| 0.3.4 | 4 / 19 | |
| 0.3.3 | 4 / 19 | |
| 0.3.2 | 4 / 19 | |
| 0.3.1 | 4 / 19 | |
| 0.3.0 | 4 / 19 | |
| 0.2.5 | 4 / 19 | |
| 0.2.4 | 4 / 19 | |
| 0.2.2 | 5 / 18 | |
| 0.2.0 | 0 / 23 |
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-23. 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.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
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.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.