@sd-jwt/jwt-status-list
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 3 / 2 | |
| 0.18.1 | 3 / 2 | |
| 0.18.0 | 3 / 2 | |
| 0.17.1 | 3 / 2 | |
| 0.17.0 | 3 / 2 | |
| 0.16.0 | 3 / 2 | |
| 0.15.0 | 3 / 2 | |
| 0.14.0 | 3 / 2 | |
| 0.13.0 | 3 / 2 | |
| 0.12.0 | 3 / 2 | |
| 0.11.0 | 3 / 2 | |
| 0.10.0 | 3 / 2 | |
| 0.9.2 | 3 / 2 | |
| 0.9.1 | 3 / 2 | |
| 0.9.0 | 3 / 2 | |
| 0.8.0 | 3 / 2 | |
| 0.7.2 | 3 / 2 | |
| 0.7.1 | 3 / 2 | |
| 0.7.0 | 3 / 2 |
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.