@nuskin/foundation-ui-components
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a declared peer dep for a React component library; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type package loaded by convention in TypeScript React libraries; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Type package loaded by convention in TypeScript React libraries; stable false positive. | ai | |
| phantom-deps | phantom-dep:cliui | AI (phantom-deps): CLI utility likely pulled in transitively via build tooling config; stable false positive for this UI component library. | ai | |
| phantom-deps | phantom-dep:react-material-ui-carousel | AI (phantom-deps): Referenced in config/story files; stable false positive for this component library. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 16 / 43 | |
| 2.2.0 | 16 / 43 | |
| 2.1.3 | 16 / 43 | |
| 2.1.2 | 16 / 43 | |
| 2.1.1 | 16 / 43 | |
| 2.1.0 | 16 / 43 |
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.