@openwallet-foundation/askar-shared
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Legitimate OpenWallet Foundation org package; provenance gap is a process concern, not a security indicator for this publisher. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 2 / 1 | |
| 0.4.3 | 2 / 1 | |
| 0.4.2 | 2 / 1 | |
| 0.4.1 | 2 / 1 | |
| 0.4.0 | 2 / 1 | |
| 0.2.5 | 1 / 1 |
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.