@amplitude/node — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

mae.capozzisdk.devdnshikevinpagtakhanjustin-fiedlerqingzhuorctbuskmanthursdayjackmccloyamp_haoliumyztiqcurtisbliujtrankelvin-lunutwanihao.yukelson.warnerajhorst_ampbrian.giori

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a known implicit dependency for TypeScript transpilation; stable for this package.	ai	2026/07/21
phantom-deps	phantom-dep:@amplitude/utils	AI (phantom-deps): Same-org scoped dependency; implicit re-export pattern is stable for Amplitude packages.	ai	2026/07/21
phantom-deps	phantom-dep:@amplitude/types	AI (phantom-deps): Same-org scoped dependency; implicit re-export pattern is stable for Amplitude packages.	ai	2026/07/21
maintainer-change	maintainer-removed	AI (maintainer-change): Corresponds to same 2021 transfer, long since settled.	ai	2026/07/21
maintainer-change	maintainer-added	AI (maintainer-change): Stale historical change, package stable for years since; no malicious behavior.	ai	2026/07/21
provenance	publisher-changed-stale	AI (provenance): Analyzer itself notes 1946d stability, inconsistent with takeover.	ai	2026/07/21
dependencies	unvetted-dep:@amplitude/types	AI (dependencies): First-party Amplitude SDK dependency within the same scoped namespace and monorepo; expected and legitimate.	ai	2026/04/26
dependencies	unvetted-dep:@amplitude/identify	AI (dependencies): First-party Amplitude SDK dependency within the same scoped namespace and monorepo; expected and legitimate.	ai	2026/04/26
dependencies	unvetted-dep:@amplitude/utils	AI (dependencies): First-party Amplitude SDK dependency within the same scoped namespace and monorepo; expected and legitimate.	ai	2026/04/26
typosquat	typosquat.levenshtein:zod	AI (typosquat): @amplitude/node is the official Amplitude Node.js SDK; the Levenshtein match to 'zod' is a coincidental false positive with no naming or functional similarity.	ai	2026/04/26

Versions (showing 32 of 32)

Version	Deps	Published
1.10.2	4 / 12	2022-09-08
1.10.1	4 / 12	2022-08-29
1.10.0	4 / 12	2022-03-31
1.9.2	4 / 12	2022-01-31
1.9.1	4 / 12	2021-11-11
1.9.0	4 / 12	2021-10-15
1.8.4	4 / 12	2021-09-22
1.8.3	4 / 12	2021-09-01
1.8.2	4 / 12	2021-08-25
1.8.1	4 / 12	2021-08-20
1.8.0	4 / 12	2021-07-27
1.7.0	4 / 12	2021-06-25
1.6.1	4 / 12	2021-05-25
1.6.0	4 / 12	2021-05-20
1.5.5	4 / 12	2021-05-12
1.5.4	4 / 12	2021-04-12
1.5.3	4 / 12	2021-03-24
1.5.2	4 / 12	2021-03-22
1.5.1	4 / 12	2021-03-15
1.5.0	4 / 11	2021-02-12
1.4.0	4 / 11	2021-02-11
1.3.3	4 / 11	2021-02-11
1.3.2	4 / 11	2021-01-30
1.3.1	4 / 11	2021-01-29
1.3.0	4 / 11	2021-01-29
1.2.0	3 / 11	2021-01-13
1.1.1	3 / 11	2020-12-18
1.0.4	3 / 10	2020-11-04
1.0.3	3 / 10	2020-10-06
1.0.2	3 / 10	2020-10-01
1.0.1	3 / 10	2020-10-01
1.0.0	3 / 10	2020-09-25

v1.10.1

1 finding

LOW No provenance attestation provenance

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

v1.10.0

2 findings

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

This version was published by a different npm account (sdk.dev) than the most recent previously approved version (justin-fiedler) on 2022-03-31. It has since remained available on npm for 1572 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.

v1.9.2

2 findings

MEDIUM Publisher changed: justin-fiedler → kevinpagtakhan (on 2022-01-31, unremoved on npm for 1631d) provenance

This version was published by a different npm account (kevinpagtakhan) than the most recent previously approved version (justin-fiedler) on 2022-01-31. It has since remained available on npm for 1631 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.

v1.9.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: qingzhuo → justin-fiedler (on 2021-11-11, known maintainer) provenance

This version was published by a different npm account (justin-fiedler) than the most recent previously approved version (qingzhuo) on 2021-11-11, but justin-fiedler is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.4

2 findings

MEDIUM Publisher changed: ajhorst_amp → qingzhuo (on 2021-09-22, unremoved on npm for 1763d) provenance

This version was published by a different npm account (qingzhuo) than the most recent previously approved version (ajhorst_amp) on 2021-09-22. It has since remained available on npm for 1763 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.

v1.8.3

1 finding

LOW No provenance attestation provenance

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

v1.8.2

1 finding

LOW No provenance attestation provenance

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

v1.8.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jtran → ajhorst_amp (on 2021-08-20, known maintainer) provenance

This version was published by a different npm account (ajhorst_amp) than the most recent previously approved version (jtran) on 2021-08-20, but ajhorst_amp is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: kelvin-lu → jtran (on 2021-06-25, known maintainer) provenance

This version was published by a different npm account (jtran) than the most recent previously approved version (kelvin-lu) on 2021-06-25, but jtran is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ajhorst_amp → kelvin-lu (on 2021-05-20, known maintainer) provenance

This version was published by a different npm account (kelvin-lu) than the most recent previously approved version (ajhorst_amp) on 2021-05-20, but kelvin-lu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.5.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ajhorst_amp → jtran (on 2021-05-12, known maintainer) provenance

This version was published by a different npm account (jtran) than the most recent previously approved version (ajhorst_amp) on 2021-05-12, but jtran is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.5.4

2 findings

MEDIUM Publisher changed: kelvin-lu → ajhorst_amp (on 2021-04-12, unremoved on npm for 1925d) provenance

This version was published by a different npm account (ajhorst_amp) than the most recent previously approved version (kelvin-lu) on 2021-04-12. It has since remained available on npm for 1925 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.

v1.5.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: kelvin-lu → hao.yu (on 2021-03-24, known maintainer) provenance

This version was published by a different npm account (hao.yu) than the most recent previously approved version (kelvin-lu) on 2021-03-24, but hao.yu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.5.2

2 findings

MEDIUM Publisher changed: kelvin-lu → ajhorst_amp (on 2021-03-22, unremoved on npm for 1946d) provenance

This version was published by a different npm account (ajhorst_amp) than the most recent previously approved version (kelvin-lu) on 2021-03-22. It has since remained available on npm for 1946 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.

v1.5.1

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.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.

v1.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.

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

2 findings

HIGH Modified vendored dependency: . (17 file(s)) vendored-integrity

The directory `.` byte-matched 84 of 101 file(s) against @amplitude/[email protected] — a version that passed review and that we hold in storage — which identifies it as a vendored copy of that package. But 17 file(s) inside it differ from that package's bytes at the same path: dist/package.json, dist/src/constants.d.ts.map, dist/src/constants.js, dist/src/constants.js.map, dist/src/nodeClient.d.ts, dist/src/nodeClient.d.ts.map, dist/src/nodeClient.js, dist/src/nodeClient.js.map, esm/package.json, esm/src/constants.d.ts.map, esm/src/constants.js, esm/src/constants.js.map, esm/src/nodeClient.d.ts, esm/src/nodeClient.d.ts.map, esm/src/nodeClient.js, esm/src/nodeClient.js.map, package.json. A vendored library that is a faithful copy except for a handful of altered files is a well-worn supply-chain shape — the surrounding real code lends the tree legitimacy while the altered files carry the payload. These files are NOT exempt from any authorship heuristic; diff them against @amplitude/[email protected] before greenflagging.

LOW No provenance attestation provenance

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

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

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

v1.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.