@amplitude/analytics-node
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): SLSA provenance attestation present; gitHead absence reflects CI pipeline change, not a supply chain risk for this org. | ai | |
| dependencies | unvetted-dep:@amplitude/analytics-core | AI (dependencies): First-party Amplitude monorepo package; stable false positive for this SDK. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 1.5.60 | 2 / 0 | |
| 1.5.59 | 2 / 0 | |
| 1.5.58 | 2 / 0 | |
| 1.5.57 | 2 / 0 | |
| 1.5.56 | 2 / 0 | |
| 1.5.55 | 2 / 0 | |
| 1.5.54 | 2 / 0 | |
| 1.5.53 | 2 / 0 | |
| 1.5.52 | 2 / 0 | |
| 1.5.51 | 2 / 0 | |
| 1.5.50 | 2 / 0 | |
| 1.5.49 | 2 / 0 | |
| 1.5.48 | 2 / 0 | |
| 1.5.47 | 2 / 0 | |
| 1.5.46 | 2 / 0 | |
| 1.5.45 | 2 / 0 | |
| 1.5.44 | 2 / 0 | |
| 1.5.43 | 2 / 0 | |
| 1.5.42 | 2 / 0 | |
| 1.5.41 | 2 / 0 | |
| 1.5.40 | 2 / 0 | |
| 1.5.39 | 2 / 0 | |
| 1.5.38 | 2 / 0 | |
| 1.5.37 | 2 / 0 | |
| 1.5.36 | 2 / 0 | |
| 1.5.35 | 2 / 0 | |
| 1.5.34 | 2 / 0 | |
| 1.5.33 | 2 / 0 | |
| 1.5.32 | 2 / 0 | |
| 1.5.31 | 2 / 0 | |
| 1.5.30 | 2 / 0 | |
| 1.5.29 | 2 / 0 | |
| 1.5.28 | 2 / 0 | |
| 1.5.27 | 2 / 0 | |
| 1.5.26 | 2 / 0 | |
| 1.5.25 | 2 / 0 | |
| 1.5.24 | 2 / 0 | |
| 1.5.23 | 2 / 0 | |
| 1.5.22 | 2 / 0 | |
| 1.5.21 | 2 / 0 | |
| 1.5.16 | 2 / 0 | |
| 1.5.15 | 2 / 0 | |
| 1.5.14 | 2 / 0 | |
| 1.5.13 | 2 / 0 | |
| 1.5.12 | 2 / 0 | |
| 1.5.11 | 2 / 0 | |
| 1.5.10 | 2 / 0 | |
| 1.5.9 | 2 / 0 | |
| 1.5.8 | 2 / 0 | |
| 1.5.7 | 2 / 0 | |
| 1.5.6 | 2 / 0 |
v1.5.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.16
2 findingsThis version was published by a different npm account than previous versions on 2025-10-15. 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.
v1.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.