@verii/db-kms
KMS plugin that uses a db
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@spencejs/spence-mongo-repos | AI (dependencies): Part of the @spencejs ecosystem used consistently across @verii packages; pinned to ~1.0.0. Stable dependency pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the LFDT-Verii monorepo ecosystem; sparse README is a documentation quality issue, not a security signal. Package has real downloads and a legitimate org backing. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 7 / 21 | |
| 1.1.2 | 7 / 21 | |
| 1.1.1 | 7 / 21 | |
| 1.1.0 | 7 / 21 | |
| 1.0.9 | 7 / 19 | |
| 1.0.8 | 7 / 19 | |
| 1.0.7 | 7 / 19 | |
| 1.0.6 | 7 / 19 | |
| 1.0.5 | 7 / 19 | |
| 1.0.4 | 7 / 19 | |
| 1.0.3 | 7 / 19 | |
| 1.0.2 | 7 / 19 | |
| 1.0.1 | 7 / 19 | |
| 1.0.0 | 7 / 19 |
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.