@storacha/access
access client
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.6.9 | 18 / 17 | |
| 1.6.8 | 18 / 17 | |
| 1.6.7 | 18 / 17 | |
| 1.6.6 | 18 / 17 | |
| 1.6.5 | 18 / 17 | |
| 1.6.2 | 18 / 17 | |
| 1.6.1 | 18 / 17 | |
| 1.6.0 | 18 / 17 | |
| 1.5.1 | 18 / 17 | |
| 1.5.0 | 18 / 17 | |
| 1.4.0 | 18 / 17 | |
| 1.3.0 | 18 / 17 | |
| 1.2.2 | 18 / 17 | |
| 1.2.1 | 18 / 17 | |
| 1.2.0 | 18 / 17 | |
| 1.1.1 | 18 / 17 | |
| 1.1.0 | 18 / 17 | |
| 1.0.5 | 18 / 17 | |
| 1.0.3 | 18 / 15 | |
| 1.0.2 | 18 / 15 | |
| 1.0.1 | 18 / 15 | |
| 1.0.0 | 18 / 15 |
v1.6.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.