@amplitude/targeting
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 | missing-githead | AI (provenance): CI/CD publish via GitHub Actions commonly omits gitHead; SLSA attestation compensates. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from manual to GitHub Actions CI/CD; expected for monorepo automation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Amplitude employees; normal team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old maintainers removed during team restructure; consistent with org-level change. | ai | |
| phantom-deps | phantom-dep:@amplitude/analytics-core | AI (phantom-deps): Imported indirectly via version script and build chain; stable for this package. | ai | |
| phantom-deps | phantom-dep:@amplitude/analytics-client-common | AI (phantom-deps): Imported indirectly via version script and build chain; stable for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.3.8 | 6 / 11 | |
| 0.3.7 | 6 / 11 | |
| 0.3.6 | 6 / 11 | |
| 0.3.5 | 6 / 11 | |
| 0.3.4 | 6 / 11 | |
| 0.3.3 | 6 / 11 | |
| 0.3.2 | 6 / 11 | |
| 0.3.1 | 6 / 11 | |
| 0.3.0 | 6 / 11 | |
| 0.2.3 | 6 / 9 | |
| 0.2.2 | 6 / 9 | |
| 0.2.1 | 6 / 9 | |
| 0.2.0 | 6 / 8 | |
| 0.1.1 | 5 / 7 |
v0.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.3.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.3.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-06-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.