@amplitude/analytics-browser
Supply chain provenance
Status for the latest visible version.
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): Transition to GitHub Actions CI/CD publishing with SLSA provenance; legitimate for @amplitude org. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance present; gitHead absence is a metadata quirk, not a security concern for this package. | ai | |
| dependencies | unvetted-dep:@amplitude/plugin-web-vitals-browser | AI (dependencies): First-party @amplitude org plugin from same monorepo. | ai | |
| dependencies | unvetted-dep:@amplitude/plugin-autocapture-browser | AI (dependencies): First-party @amplitude org plugin from same monorepo. | ai | |
| dependencies | unvetted-dep:@amplitude/plugin-network-capture-browser | AI (dependencies): First-party @amplitude org plugin from same monorepo. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Fires in minified GTM bundle; expected pattern for browser analytics SDK, not obfuscation for evasion. | ai | |
| dependencies | unvetted-dep:@amplitude/plugin-page-view-tracking-browser | AI (dependencies): First-party @amplitude org plugin from same monorepo. | ai | |
| dependencies | unvetted-dep:@amplitude/plugin-page-url-enrichment-browser | AI (dependencies): First-party @amplitude org plugin from same monorepo. | ai | |
| dependencies | unvetted-dep:@amplitude/plugin-event-property-attribution-browser | AI (dependencies): First-party @amplitude org plugin from same monorepo. | ai | |
| dependencies | unvetted-dep:@amplitude/plugin-custom-enrichment-browser | AI (dependencies): First-party @amplitude org plugin from same monorepo. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): In minified GTM bundle; standard minifier/bundler output for this SDK. | ai |
Versions (showing 74 of 174)
| Version | Deps | Published |
|---|---|---|
| 2.17.9 | 6 / 11 | |
| 2.17.8 | 6 / 11 | |
| 2.17.6 | 6 / 11 | |
| 2.17.5 | 6 / 11 | |
| 2.17.4 | 6 / 11 | |
| 2.17.3 | 6 / 11 | |
| 2.17.2 | 6 / 11 | |
| 2.17.1 | 6 / 11 | |
| 2.17.0 | 6 / 11 | |
| 2.16.1 | 5 / 11 | |
| 2.16.0 | 5 / 11 | |
| 2.15.0 | 5 / 11 | |
| 2.14.0 | 5 / 11 | |
| 2.13.3 | 5 / 11 | |
| 2.13.2 | 5 / 11 | |
| 2.13.1 | 5 / 11 | |
| 2.13.0 | 5 / 11 | |
| 2.12.2 | 5 / 11 | |
| 2.12.1 | 5 / 11 | |
| 2.12.0 | 6 / 11 | |
| 2.11.13 | 7 / 11 | |
| 2.11.12 | 7 / 11 | |
| 2.11.11 | 7 / 11 | |
| 2.11.10 | 7 / 11 | |
| 2.11.9 | 7 / 11 | |
| 2.11.8 | 7 / 11 | |
| 2.11.7 | 7 / 11 | |
| 2.11.6 | 7 / 11 | |
| 2.11.5 | 7 / 11 | |
| 2.11.4 | 7 / 11 | |
| 2.11.3 | 7 / 11 | |
| 2.11.2 | 7 / 11 | |
| 2.11.1 | 7 / 11 | |
| 2.11.0 | 7 / 11 | |
| 2.10.0 | 7 / 11 | |
| 2.9.3 | 5 / 10 | |
| 2.9.2 | 5 / 10 | |
| 2.9.1 | 5 / 10 | |
| 2.9.0 | 5 / 10 | |
| 2.8.1 | 5 / 10 | |
| 2.8.0 | 5 / 10 | |
| 2.7.4 | 5 / 10 | |
| 2.7.3 | 5 / 10 | |
| 2.7.2 | 5 / 10 | |
| 2.7.1 | 5 / 10 | |
| 2.7.0 | 5 / 10 | |
| 2.6.2 | 6 / 10 | |
| 2.6.1 | 6 / 10 | |
| 2.6.0 | 6 / 10 | |
| 2.5.3 | 6 / 10 | |
| 2.5.2 | 6 / 10 | |
| 2.5.1 | 6 / 10 | |
| 2.5.0 | 6 / 10 | |
| 2.4.1 | 6 / 10 | |
| 2.4.0 | 6 / 10 | |
| 2.3.8 | 6 / 10 | |
| 2.3.7 | 6 / 10 | |
| 2.3.6 | 6 / 10 | |
| 2.3.5 | 6 / 10 | |
| 2.3.4 | 6 / 10 | |
| 2.3.3 | 6 / 10 | |
| 2.3.2 | 6 / 10 | |
| 2.3.1 | 6 / 10 | |
| 2.3.0 | 6 / 10 | |
| 2.2.3 | 6 / 10 | |
| 2.2.2 | 6 / 10 | |
| 2.2.1 | 6 / 10 | |
| 2.2.0 | 6 / 10 | |
| 2.1.3 | 6 / 10 | |
| 2.1.2 | 6 / 10 | |
| 2.1.1 | 6 / 10 | |
| 2.1.0 | 6 / 10 | |
| 2.0.1 | 6 / 10 | |
| 2.0.0 | 6 / 10 |
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.