@podium/schemas
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.2.1 | 2 / 10 | |
| 5.2.0 | 2 / 10 | |
| 5.1.2 | 2 / 10 | |
| 5.1.1 | 2 / 10 | |
| 5.1.0 | 2 / 9 | |
| 5.0.6 | 2 / 15 | |
| 5.0.5 | 2 / 15 | |
| 5.0.4 | 2 / 15 | |
| 5.0.3 | 2 / 15 | |
| 5.0.2 | 2 / 15 | |
| 5.0.1 | 2 / 14 | |
| 5.0.0 | 2 / 14 |
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.