@snowplow/browser-tracker-core
Core functionality for Snowplow Browser trackers
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Snowplow org package; lack of provenance is consistent across their published versions. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 4.9.0 | 3 / 20 | |
| 4.8.4 | 3 / 20 | |
| 4.8.3 | 3 / 20 | |
| 4.8.2 | 3 / 22 | |
| 4.8.1 | 3 / 22 | |
| 4.8.0 | 3 / 22 | |
| 4.7.0 | 3 / 22 | |
| 4.6.9 | 4 / 23 | |
| 4.6.8 | 4 / 23 | |
| 4.6.7 | 4 / 23 | |
| 4.6.6 | 4 / 23 | |
| 4.6.5 | 4 / 23 | |
| 4.6.4 | 4 / 23 | |
| 4.6.3 | 4 / 23 | |
| 4.6.2 | 4 / 23 | |
| 4.6.1 | 4 / 23 | |
| 4.6.0 | 4 / 23 | |
| 4.5.0 | 4 / 23 | |
| 4.4.0 | 4 / 23 | |
| 4.3.1 | 4 / 23 | |
| 4.3.0 | 4 / 23 | |
| 4.2.0 | 4 / 23 | |
| 4.1.0 | 4 / 23 | |
| 4.0.4 | 4 / 23 | |
| 4.0.3 | 4 / 23 | |
| 4.0.2 | 4 / 23 | |
| 4.0.1 | 4 / 23 | |
| 4.0.0 | 4 / 23 |
v4.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.