@amplitude/identify
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Amplitude SDK package published before provenance attestation was common practice; absence is expected and not a risk signal for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.10.2 | 3 / 7 | |
| 1.10.1 | 3 / 7 | |
| 1.10.0 | 3 / 7 | |
| 1.9.2 | 3 / 7 | |
| 1.9.1 | 3 / 7 | |
| 1.9.0 | 3 / 7 | |
| 1.8.4 | 3 / 7 | |
| 1.8.2 | 3 / 7 | |
| 1.8.1 | 3 / 7 | |
| 1.8.0 | 3 / 7 | |
| 1.7.0 | 3 / 7 | |
| 1.6.1 | 3 / 7 | |
| 1.6.0 | 3 / 7 | |
| 1.5.5 | 3 / 7 | |
| 1.5.4 | 3 / 7 | |
| 1.5.3 | 3 / 7 | |
| 1.5.2 | 3 / 7 | |
| 1.5.1 | 3 / 7 | |
| 1.5.0 | 3 / 6 | |
| 1.4.0 | 3 / 6 | |
| 1.3.2 | 3 / 6 | |
| 1.3.1 | 2 / 6 | |
| 1.3.0 | 1 / 6 |
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
2 findingsThis version was published by a different npm account (sdk.dev) than the most recent previously approved version (kevinpagtakhan) 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kelvin-lu) than the most recent previously approved version (jtran) 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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ajhorst_amp) than the most recent previously approved version (hao.yu) on 2021-04-12, 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.5.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hao.yu) than the most recent previously approved version (ajhorst_amp) 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 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.