@amplitude/experiment-js-client
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): Migrated to GitHub Actions CI/CD publishing with SLSA provenance; legitimate for @amplitude org. | ai | |
| phantom-deps | phantom-dep:unfetch | AI (phantom-deps): Bundled dependency; not directly imported in source but legitimately used via build pipeline. | ai | |
| phantom-deps | phantom-dep:base64-js | AI (phantom-deps): Bundled dependency; not directly imported in source but legitimately used via build pipeline. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.21.3 | 5 / 4 | |
| 1.21.2 | 5 / 4 | |
| 1.21.1 | 5 / 4 | |
| 1.21.0 | 5 / 4 | |
| 1.20.4 | 5 / 4 | |
| 1.20.3 | 5 / 4 | |
| 1.20.2 | 5 / 4 | |
| 1.20.1 | 5 / 4 | |
| 1.20.0 | 5 / 4 | |
| 1.19.0 | 5 / 4 | |
| 1.17.1 | 5 / 4 | |
| 1.16.1 | 5 / 2 | |
| 1.15.6 | 5 / 2 | |
| 1.15.5 | 5 / 2 | |
| 1.15.4 | 5 / 2 | |
| 1.15.3 | 5 / 2 | |
| 1.15.2 | 5 / 2 | |
| 1.15.1 | 5 / 2 | |
| 1.15.0 | 5 / 2 | |
| 1.14.1 | 5 / 2 | |
| 1.14.0 | 5 / 2 | |
| 1.13.2 | 5 / 2 | |
| 1.13.1 | 5 / 2 | |
| 1.13.0 | 5 / 2 | |
| 1.12.3 | 5 / 2 | |
| 1.12.2 | 5 / 2 | |
| 1.12.1 | 5 / 2 | |
| 1.12.0 | 5 / 2 | |
| 1.11.0 | 5 / 2 | |
| 1.10.2 | 5 / 2 | |
| 1.10.1 | 5 / 2 |
v1.21.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.