@chubbyts/chubbyts-log-types
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted long-tenured publisher; benign types-only release, no behavioral change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Low-traffic utility package with sparse but consistent legitimate releases historically. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 0 / 9 | |
| 3.1.1 | 0 / 9 | |
| 3.1.0 | 0 / 9 | |
| 3.0.3 | 0 / 9 | |
| 3.0.1 | 0 / 9 | |
| 3.0.0 | 0 / 9 |
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dominikzogg.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.