@snowplow/snowtype
A code generator CLI for faster and type-safe Snowplow tracking code
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 | publisher-changed | AI (provenance): Snowplow org migrated publishing to GitHub Actions CI/CD; consistent with org-level automation, not account compromise. | ai | |
| dependencies | unvetted-dep:@snowplow/snowtype-core | AI (dependencies): First-party Snowplow sibling package in the same org namespace; stable false positive for this package. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.17.3 | 18 / 16 | |
| 0.17.2 | 18 / 17 | |
| 0.17.1 | 18 / 17 | |
| 0.17.0 | 18 / 17 | |
| 0.16.0 | 18 / 17 | |
| 0.15.3 | 18 / 17 | |
| 0.15.2 | 18 / 17 | |
| 0.15.1 | 18 / 17 | |
| 0.15.0 | 18 / 17 | |
| 0.14.0 | 18 / 17 | |
| 0.13.4 | 18 / 17 | |
| 0.13.3 | 18 / 17 | |
| 0.13.2 | 18 / 17 | |
| 0.13.1 | 18 / 17 | |
| 0.13.0 | 18 / 17 | |
| 0.12.4 | 18 / 17 | |
| 0.12.3 | 18 / 17 | |
| 0.12.2 | 17 / 17 | |
| 0.12.1 | 17 / 17 | |
| 0.12.0 | 17 / 17 | |
| 0.11.0 | 16 / 17 | |
| 0.10.2 | 16 / 16 | |
| 0.10.1 | 15 / 16 | |
| 0.10.0 | 15 / 16 | |
| 0.9.0 | 15 / 16 | |
| 0.8.4 | 15 / 16 | |
| 0.8.3 | 15 / 16 | |
| 0.8.2 | 15 / 15 | |
| 0.8.1 | 15 / 15 | |
| 0.8.0 | 14 / 14 | |
| 0.7.1 | 13 / 14 | |
| 0.7.0 | 13 / 14 | |
| 0.6.0 | 13 / 14 | |
| 0.5.1 | 13 / 14 | |
| 0.5.0 | 13 / 14 | |
| 0.4.2 | 13 / 14 | |
| 0.4.1 | 13 / 14 | |
| 0.4.0 | 12 / 14 |
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.