@amityco/ui-kit-open-source
React Ui-Kit for Amity Social Cloud
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:linkifyjs | AI (phantom-deps): linkifyjs is declared in dependencies; likely imported indirectly or via config. | ai | |
| phantom-deps | phantom-dep:react-aria | AI (phantom-deps): react-aria is declared in dependencies; likely imported indirectly or via config. | ai | |
| phantom-deps | phantom-dep:modern-normalize | AI (phantom-deps): CSS normalize imported via config/build tooling, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@livekit/track-processors | AI (phantom-deps): Declared dep; likely dynamically imported or used conditionally. | ai | |
| phantom-deps | phantom-dep:@livekit/components-styles | AI (phantom-deps): CSS styles package imported via config, not direct JS import. | ai |
v4.16.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 (platform-butler) than the most recent previously approved version (ekoapp) on 2026-05-28, but platform-butler 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.
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.