@giteeteam/plugin-sdk
Giteeteam plugin sdk
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.9.7 | 1 / 6 | |
| 0.9.6 | 1 / 6 | |
| 0.9.5 | 1 / 6 | |
| 0.9.4 | 1 / 6 | |
| 0.9.3 | 1 / 6 | |
| 0.9.1 | 1 / 6 | |
| 0.9.0 | 1 / 6 | |
| 0.8.0 | 1 / 6 | |
| 0.6.9 | 1 / 6 | |
| 0.6.8 | 1 / 6 | |
| 0.6.7 | 1 / 6 | |
| 0.6.6 | 1 / 6 | |
| 0.6.5 | 1 / 6 | |
| 0.6.4 | 1 / 6 | |
| 0.6.3 | 1 / 6 | |
| 0.6.1 | 1 / 6 | |
| 0.6.0 | 1 / 6 |
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.