@amplitude/utils
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@amplitude/eslint-config-typescript | AI (dependencies): Same-org lint config, dev-tooling only, not a security risk. | ai | |
| phantom-deps | phantom-dep:@amplitude/eslint-config-typescript | AI (phantom-deps): Same-org config package, expected to be unused at runtime. | ai | |
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer; benign for this official package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the official Amplitude SDK monorepo; sparse README and missing keywords are a documentation style choice, not spam indicators. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.10.2 | 2 / 10 | |
| 1.10.1 | 2 / 10 | |
| 1.10.0 | 2 / 10 | |
| 1.9.2 | 2 / 10 | |
| 1.9.1 | 2 / 10 | |
| 1.9.0 | 2 / 10 | |
| 1.8.4 | 2 / 10 | |
| 1.8.2 | 2 / 10 | |
| 1.8.1 | 2 / 10 | |
| 1.8.0 | 2 / 10 | |
| 1.7.0 | 2 / 10 | |
| 1.6.1 | 2 / 10 | |
| 1.5.5 | 2 / 10 | |
| 1.5.4 | 2 / 10 | |
| 1.5.3 | 2 / 10 | |
| 1.5.2 | 2 / 10 | |
| 1.5.1 | 2 / 10 | |
| 1.5.0 | 2 / 9 | |
| 1.3.1 | 2 / 9 | |
| 1.3.0 | 2 / 9 | |
| 1.2.0 | 2 / 9 | |
| 1.1.1 | 2 / 9 | |
| 1.1.0 | 3 / 8 | |
| 1.0.5 | 1 / 8 | |
| 1.0.4 | 1 / 8 | |
| 1.0.3 | 1 / 4 | |
| 1.0.2 | 1 / 4 | |
| 1.0.0 | 1 / 4 |
v1.10.1
1 findingPackage 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.
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 (qingzhuo) 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
2 findingsPackage 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
2 findingsThis version was published by a different npm account (qingzhuo) than the most recent previously approved version (ajhorst_amp) on 2021-10-15. It has since remained available on npm for 1740 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
2 findingsPackage 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-25, 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.1
2 findingsPackage 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
2 findingsPackage 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-07-27, 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.7.0
2 findingsPackage 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
2 findingsPackage 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 (ajhorst_amp) on 2021-05-25, 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 findingsPackage 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 findingsPackage 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 findingsPackage 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jtran.
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 2020-11-05, 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.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.