@nsshunt/stskafka
STS Kafka
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 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 1.0.74 | 4 / 10 | |
| 1.0.73 | 4 / 10 | |
| 1.0.72 | 4 / 10 | |
| 1.0.71 | 4 / 10 | |
| 1.0.70 | 4 / 10 | |
| 1.0.69 | 4 / 10 | |
| 1.0.68 | 4 / 10 | |
| 1.0.67 | 4 / 10 | |
| 1.0.66 | 4 / 10 | |
| 1.0.65 | 4 / 10 | |
| 1.0.64 | 4 / 10 | |
| 1.0.63 | 4 / 10 | |
| 1.0.62 | 4 / 10 | |
| 1.0.61 | 4 / 10 | |
| 1.0.60 | 4 / 10 | |
| 1.0.59 | 4 / 10 | |
| 1.0.58 | 5 / 9 | |
| 1.0.57 | 5 / 9 | |
| 1.0.56 | 5 / 9 | |
| 1.0.55 | 5 / 9 | |
| 1.0.49 | 5 / 9 | |
| 1.0.48 | 5 / 9 | |
| 1.0.47 | 5 / 9 | |
| 1.0.46 | 5 / 9 | |
| 1.0.45 | 5 / 9 | |
| 1.0.44 | 5 / 9 | |
| 1.0.43 | 5 / 9 | |
| 1.0.42 | 5 / 9 | |
| 1.0.40 | 5 / 9 | |
| 1.0.39 | 5 / 9 | |
| 1.0.38 | 5 / 9 | |
| 1.0.37 | 5 / 9 | |
| 1.0.36 | 5 / 10 | |
| 1.0.35 | 5 / 10 | |
| 1.0.34 | 5 / 10 | |
| 1.0.33 | 5 / 10 | |
| 1.0.32 | 5 / 10 | |
| 1.0.31 | 5 / 10 | |
| 1.0.30 | 5 / 10 | |
| 1.0.29 | 5 / 10 | |
| 1.0.28 | 5 / 10 | |
| 1.0.12 | 5 / 16 | |
| 1.0.11 | 5 / 16 | |
| 1.0.10 | 5 / 16 | |
| 1.0.6 | 5 / 16 | |
| 1.0.3 | 5 / 16 |
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.