analytics-client
Supply chain provenance
Status for the latest visible version.
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 balena.io package with long history; absence of provenance is consistent across all versions. | ai | |
| dependencies | unvetted-dep:@amplitude/engagement-browser | AI (dependencies): Legitimate Amplitude SDK plugin; consistent with analytics-client's purpose. | ai | |
| dependencies | unvetted-dep:@amplitude/plugin-user-agent-enrichment-browser | AI (dependencies): Legitimate Amplitude SDK plugin; consistent with analytics-client's purpose. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 4 / 13 | |
| 3.1.3 | 4 / 13 | |
| 3.1.2 | 4 / 13 | |
| 3.1.1 | 4 / 13 | |
| 3.1.0 | 4 / 13 | |
| 3.0.0 | 3 / 13 |
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.