← Home

@amplitude/analytics-client-common

npm Repository Homepage
100
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

curtisbliukelson.warnersdk.deveric_amplitudedaniel-graham-amplitudejjwang123

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Amplitude migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern for this org. ai
npm-metadata no-description AI (npm-metadata): Amplitude's package.json intentionally has empty description; stable false positive for this package. ai

Versions (showing 100 of 113)

Version Deps Published
2.4.58 4 / 0
2.4.57 4 / 0
2.4.56 4 / 0
2.4.55 4 / 0
2.4.54 4 / 0
2.4.53 4 / 0
2.4.52 4 / 0
2.4.51 4 / 0
2.4.50 4 / 0
2.4.49 4 / 0
2.4.48 4 / 0
2.4.47 4 / 0
2.4.46 4 / 0
2.4.45 4 / 0
2.4.44 4 / 0
2.4.43 4 / 0
2.4.42 4 / 0
2.4.41 4 / 0
2.4.36 4 / 0
2.4.34 4 / 0
2.4.33 4 / 0
2.4.31 4 / 0
2.4.30 4 / 0
2.4.28 4 / 0
2.4.22 4 / 0
2.4.21 4 / 0
2.4.20 4 / 0
2.4.19 4 / 0
2.4.18 4 / 0
2.4.17 4 / 0
2.4.16 4 / 0
2.4.15 4 / 0
2.4.14 4 / 0
2.4.13 4 / 0
2.4.12 4 / 0
2.4.11 4 / 0
2.4.10 4 / 0
2.4.9 4 / 0
2.4.8 4 / 0
2.4.7 4 / 0
2.4.6 4 / 0
2.4.5 4 / 0
2.4.4 4 / 0
2.4.3 4 / 0
2.4.2 4 / 0
2.4.1 4 / 0
2.4.0 4 / 0
2.3.42 4 / 0
2.3.41 4 / 0
2.3.40 4 / 0
2.3.39 4 / 0
2.3.38 4 / 0
2.3.37 4 / 0
2.3.36 4 / 0
2.3.35 4 / 0
2.3.34 4 / 0
2.3.33 4 / 0
2.3.32 4 / 0
2.3.31 4 / 0
2.3.30 4 / 0
2.3.29 4 / 0
2.3.28 4 / 0
2.3.27 4 / 0
2.3.26 4 / 0
2.3.25 4 / 0
2.3.24 4 / 0
2.3.23 4 / 0
2.3.21 4 / 0
2.3.20 4 / 0
2.3.19 4 / 0
2.3.18 4 / 0
2.3.17 4 / 0
2.3.16 4 / 0
2.3.15 4 / 0
2.3.14 4 / 0
2.3.13 4 / 0
2.3.12 4 / 0
2.3.11 4 / 0
2.3.10 4 / 0
2.3.9 4 / 0
2.3.8 4 / 0
2.3.7 4 / 0
2.3.6 4 / 0
2.3.5 4 / 0
2.3.4 4 / 0
2.3.3 4 / 0
2.3.2 4 / 0
2.3.1 4 / 0
2.3.0 4 / 0
2.2.4 4 / 0
2.2.3 4 / 0
2.2.2 4 / 0
2.2.1 4 / 0
2.2.0 4 / 0
2.1.6 4 / 0
2.1.5 4 / 0
2.1.4 4 / 0
2.1.3 4 / 0
2.1.2 4 / 0
2.1.1 4 / 0
Showing 100 of 113 Next page →

v2.4.58

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.57

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.56

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.55

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.54

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.53

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.52

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.3.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.