dynamodb-toolbox
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD with SLSA provenance; standard automation pattern. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 2.10.1 | 1 / 27 | |
| 2.10.0 | 1 / 27 | |
| 2.9.0 | 1 / 27 | |
| 2.8.0 | 1 / 27 | |
| 2.7.4 | 1 / 27 | |
| 2.7.2 | 1 / 27 | |
| 2.7.1 | 1 / 27 | |
| 2.7.0 | 1 / 27 | |
| 2.6.6 | 1 / 27 | |
| 2.6.5 | 1 / 27 | |
| 2.6.4 | 1 / 27 | |
| 2.6.3 | 1 / 27 | |
| 2.6.2 | 1 / 27 | |
| 2.6.1 | 1 / 27 | |
| 2.6.0 | 1 / 27 | |
| 2.5.0 | 1 / 27 | |
| 2.4.4 | 1 / 26 | |
| 2.4.3 | 1 / 26 | |
| 2.4.2 | 1 / 26 | |
| 2.4.1 | 1 / 26 | |
| 2.4.0 | 1 / 26 | |
| 2.3.0 | 1 / 26 | |
| 2.2.2 | 1 / 25 | |
| 2.2.1 | 1 / 25 | |
| 2.2.0 | 1 / 25 | |
| 2.1.2 | 1 / 25 | |
| 2.1.1 | 1 / 25 | |
| 2.1.0 | 1 / 25 | |
| 2.0.0 | 1 / 25 |
v2.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.