@amityco/ui-kit
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 a direct runtime dep in package.json; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:react-aria | AI (phantom-deps): react-aria is a direct runtime dep in package.json; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:modern-normalize | AI (phantom-deps): modern-normalize is a direct runtime dep in package.json; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@livekit/track-processors | AI (phantom-deps): Listed as direct runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@livekit/components-styles | AI (phantom-deps): Listed as direct runtime dep; phantom-dep heuristic false positive. | 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.