amplitude-js No license 47 versions

amplitude-js

npm Repository Homepage

47

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

blazzyjtranmanthursdaysputhamp_haoliukelvin-lubrian.giorisdk.dev

Keywords

analyticsamplitude

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed-stale	AI (provenance): Stale takeover signature; publisher unchanged for years across many versions.	ai	2026/07/19
publish-pattern	new-deps-added	AI (publish-pattern): Added dep is Amplitude's own first-party package.	ai	2026/07/19
phantom-deps	phantom-dep:@babel/runtime	AI (phantom-deps): Framework-convention dep, not a real risk.	ai	2026/07/19

Versions (showing 47 of 47)

Version	Deps	Published
8.21.10	6 / 46	2026-02-11
8.21.9	6 / 45	2023-04-27
8.21.8	6 / 45	2023-04-04
8.21.7	6 / 45	2023-03-23
8.21.6	6 / 46	2023-03-07
8.21.5	6 / 46	2023-02-16
8.21.4	6 / 46	2023-01-18
8.21.3	6 / 46	2022-12-09
8.21.2	6 / 46	2022-10-25
8.21.1	6 / 46	2022-09-22
8.21.0	6 / 46	2022-09-08
8.20.1	6 / 46	2022-09-01
8.20.0	6 / 46	2022-08-24
8.19.0	6 / 46	2022-07-25
8.18.5	6 / 46	2022-06-24
8.18.4	6 / 46	2022-05-31
8.18.3	6 / 46	2022-05-24
8.18.2	6 / 46	2022-05-12
8.18.1	6 / 46	2022-04-06
8.18.0	6 / 46	2022-03-31
8.17.0	6 / 46	2022-02-10
8.16.1	5 / 46	2022-01-28
8.16.0	5 / 46	2022-01-21
8.15.1	5 / 46	2022-01-18
8.15.0	5 / 46	2022-01-07
8.14.1	5 / 46	2021-12-23
8.14.0	5 / 46	2021-12-21
8.13.1	5 / 45	2021-12-03
8.13.0	4 / 46	2021-11-30
8.12.0	4 / 46	2021-11-18
8.11.1	4 / 46	2021-11-16
8.11.0	4 / 46	2021-11-16
8.10.0	4 / 46	2021-11-12
8.9.1	4 / 46	2021-11-02
8.9.0	4 / 46	2021-10-28
8.8.0	4 / 46	2021-09-22
8.7.0	4 / 46	2021-09-16
8.6.0	4 / 46	2021-09-08
8.5.0	4 / 46	2021-08-13
8.4.0	4 / 46	2021-07-30
8.3.1	4 / 46	2021-06-10
8.3.0	4 / 46	2021-05-26
8.2.3	4 / 46	2021-05-18
8.2.1	4 / 46	2021-04-30
8.2.0	4 / 46	2021-04-28
8.1.0	4 / 46	2021-03-19
8.0.0	4 / 46	2021-03-15

v8.21.10

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.

v8.21.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.20.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.18.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.18.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.18.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.18.2

2 findings

MEDIUM Publisher changed: jtran → sdk.dev (on 2022-05-12, unremoved on npm for 1528d) provenance

This version was published by a different npm account (sdk.dev) than the most recent previously approved version (jtran) on 2022-05-12. It has since remained available on npm for 1528 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.18.1

2 findings

MEDIUM Publisher changed: jtran → sdk.dev (on 2022-04-06, unremoved on npm for 1565d) provenance

This version was published by a different npm account (sdk.dev) than the most recent previously approved version (jtran) on 2022-04-06. It has since remained available on npm for 1565 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.18.0

2 findings

MEDIUM Publisher changed: jtran → sdk.dev (on 2022-03-31, unremoved on npm for 1570d) provenance

This version was published by a different npm account (sdk.dev) than the most recent previously approved version (jtran) on 2022-03-31. It has since remained available on npm for 1570 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.15.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.14.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.13.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.1.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.

v8.0.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.