@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, 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 |
|---|---|---|---|---|
| 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 |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.19.1 | 46 / 61 | |
| 4.19.0 | 46 / 61 | |
| 4.18.0 | 46 / 61 | |
| 4.17.3 | 46 / 63 | |
| 4.17.2 | 46 / 63 | |
| 4.17.1 | 46 / 63 | |
| 4.16.3 | 46 / 63 | |
| 4.16.0 | 46 / 63 | |
| 4.15.0 | 46 / 63 | |
| 4.1.0 | 39 / 59 | |
| 4.0.2 | 39 / 59 |
v4.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.