@daocloud-proto/kpanda
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 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.48.1 | 0 / 0 | |
| 0.48.0 | 0 / 0 | |
| 0.47.1 | 0 / 0 | |
| 0.47.0 | 0 / 0 | |
| 0.46.1 | 0 / 0 | |
| 0.46.0 | 0 / 0 | |
| 0.45.0 | 0 / 0 | |
| 0.44.0 | 0 / 0 | |
| 0.43.3 | 0 / 0 | |
| 0.43.2 | 0 / 0 | |
| 0.43.1 | 0 / 0 | |
| 0.43.0 | 0 / 0 | |
| 0.42.1 | 0 / 0 | |
| 0.42.0 | 0 / 0 | |
| 0.41.0 | 0 / 0 | |
| 0.40.2 | 0 / 0 | |
| 0.40.1 | 0 / 0 | |
| 0.40.0 | 0 / 0 | |
| 0.39.1 | 0 / 0 | |
| 0.39.0 | 0 / 0 | |
| 0.38.0 | 0 / 0 | |
| 0.37.0 | 0 / 0 | |
| 0.36.0 | 0 / 0 | |
| 0.35.0 | 0 / 0 | |
| 0.34.0 | 0 / 0 | |
| 0.33.2 | 0 / 0 | |
| 0.33.1 | 0 / 0 | |
| 0.33.0 | 0 / 0 | |
| 0.32.2 | 0 / 0 | |
| 0.32.1 | 0 / 0 | |
| 0.32.0 | 0 / 0 | |
| 0.31.1 | 0 / 0 | |
| 0.31.0 | 0 / 0 | |
| 0.30.2 | 0 / 0 | |
| 0.30.1 | 0 / 0 | |
| 0.30.0 | 0 / 0 | |
| 0.29.1 | 0 / 0 | |
| 0.29.0 | 0 / 0 | |
| 0.28.1 | 0 / 0 | |
| 0.28.0 | 0 / 0 | |
| 0.27.0 | 0 / 0 | |
| 0.24.3 | 0 / 0 |
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.