@amityco/ts-sdk
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): Established scoped SDK (@amityco/ts-sdk) with 1738 days history; Levenshtein match to aws-sdk is coincidental, not impersonation. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.24.0 | 10 / 25 | |
| 7.23.0 | 10 / 25 | |
| 7.22.0 | 10 / 25 | |
| 7.21.0 | 10 / 25 | |
| 7.20.0 | 10 / 25 | |
| 7.19.0 | 10 / 25 | |
| 7.18.0 | 10 / 25 | |
| 7.14.0 | 10 / 24 | |
| 7.13.0 | 10 / 22 | |
| 7.12.0 | 10 / 22 | |
| 6.35.3 | 10 / 23 |
v7.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.