@amplitude/plugin-page-view-tracking-browser
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 | publisher-changed | AI (provenance): Migration from individual npm account to GitHub Actions CI/CD; SLSA provenance confirms legitimate org pipeline. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Amplitude org regularly rotates npm team members; consistent with internal team management. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass removal consistent with Amplitude org restructuring npm access, not a hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @amplitude/analytics-core is a first-party Amplitude package; not a suspicious third-party dep. | ai | |
| provenance | missing-githead | AI (provenance): Published via GitHub Actions with SLSA provenance; gitHead absence is a CI config change, not a threat. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo with 249 versions; dormancy reflects per-package publish cadence, not account compromise. | ai |
Versions (showing 51 of 152)
| Version | Deps | Published |
|---|---|---|
| 2.11.11 | 2 / 7 | |
| 2.11.10 | 2 / 7 | |
| 2.11.9 | 2 / 7 | |
| 2.11.8 | 2 / 7 | |
| 2.11.7 | 2 / 7 | |
| 2.11.6 | 2 / 7 | |
| 2.11.5 | 2 / 7 | |
| 2.11.4 | 2 / 7 | |
| 2.11.3 | 2 / 7 | |
| 2.11.2 | 2 / 7 | |
| 2.11.1 | 2 / 7 | |
| 2.11.0 | 2 / 7 | |
| 2.10.2 | 2 / 7 | |
| 2.10.1 | 2 / 7 | |
| 2.10.0 | 2 / 7 | |
| 2.9.6 | 2 / 7 | |
| 2.9.5 | 2 / 7 | |
| 2.9.4 | 2 / 7 | |
| 2.9.3 | 2 / 7 | |
| 2.9.2 | 2 / 7 | |
| 2.9.1 | 2 / 7 | |
| 2.9.0 | 2 / 7 | |
| 2.8.7 | 2 / 7 | |
| 2.8.6 | 2 / 7 | |
| 2.8.5 | 2 / 7 | |
| 2.8.4 | 2 / 7 | |
| 2.8.3 | 2 / 7 | |
| 2.8.2 | 2 / 7 | |
| 2.8.1 | 2 / 7 | |
| 2.8.0 | 2 / 7 | |
| 2.7.3 | 2 / 7 | |
| 2.7.2 | 2 / 7 | |
| 2.7.1 | 2 / 7 | |
| 2.7.0 | 2 / 7 | |
| 2.6.12 | 2 / 7 | |
| 2.6.11 | 2 / 7 | |
| 2.6.10 | 2 / 7 | |
| 2.6.9 | 2 / 7 | |
| 2.6.8 | 2 / 7 | |
| 2.6.7 | 2 / 7 | |
| 2.6.6 | 2 / 7 | |
| 2.6.5 | 2 / 7 | |
| 2.6.4 | 2 / 7 | |
| 2.6.3 | 2 / 7 | |
| 2.6.2 | 2 / 7 | |
| 2.6.1 | 2 / 7 | |
| 2.6.0 | 2 / 7 | |
| 2.5.7 | 2 / 7 | |
| 2.5.6 | 2 / 7 | |
| 2.5.5 | 2 / 7 | |
| 2.5.4 | 2 / 7 |
v2.11.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.