@amityco/ts-sdk-react-native
Amity Social Cloud Typescript 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher has 32 approved/0 rejected track record; no behavioral change in diff. | ai | |
| phantom-deps | phantom-dep:mime | AI (phantom-deps): Config-file reference only, not a security concern. | ai | |
| phantom-deps | phantom-dep:ts-jest | AI (phantom-deps): Config-file reference only, not a security concern. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 7.24.0 | 14 / 28 | |
| 7.23.0 | 14 / 28 | |
| 7.22.0 | 14 / 28 | |
| 7.21.1 | 14 / 28 | |
| 7.21.0 | 14 / 28 | |
| 7.20.0 | 14 / 28 | |
| 7.19.0 | 14 / 28 | |
| 7.18.0 | 14 / 28 | |
| 7.17.0 | 14 / 28 | |
| 7.15.1 | 14 / 27 | |
| 7.14.0 | 14 / 27 | |
| 7.13.0 | 14 / 25 | |
| 7.12.0 | 14 / 25 | |
| 7.11.0 | 14 / 25 |
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.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. 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.15.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. 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.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. Consider requesting the maintainer enable provenance via CI/CD.