@payloadcms/db-mongodb
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): danribbens is an established Payload team publisher with 112 approved packages; internal maintainer rotation within payloadcms org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): v2.0.0 is a legacy/LTS branch of an active monorepo; dormancy reflects branching strategy, not account takeover. | ai | |
| phantom-deps | phantom-dep:bson-objectid | AI (phantom-deps): Declared in package.json and referenced in config; phantom-dep heuristic fires on indirect usage patterns. | ai |
Versions (showing 17 of 117)
| Version | Deps | Published |
|---|---|---|
| 3.9.0 | 6 / 5 | |
| 3.8.0 | 6 / 5 | |
| 3.7.0 | 6 / 5 | |
| 3.6.0 | 6 / 5 | |
| 3.5.0 | 6 / 5 | |
| 3.4.0 | 6 / 5 | |
| 3.3.0 | 6 / 5 | |
| 3.2.2 | 6 / 5 | |
| 3.2.1 | 6 / 5 | |
| 3.2.0 | 6 / 5 | |
| 3.1.1 | 6 / 5 | |
| 3.1.0 | 6 / 5 | |
| 3.0.2 | 6 / 5 | |
| 3.0.1 | 6 / 5 | |
| 3.0.0 | 6 / 5 | |
| 2.0.1 | 9 / 5 | |
| 2.0.0 | 9 / 5 |
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.