← Home

@new-ui/foundations

npm Repository Homepage

New UI foundations

10
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

planetabhistevepaul

Keywords

foundationstypographycolorsspacingsuimodulartypedesign-tokensmobileresetnew

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@new-ui/reset AI (phantom-deps): Monorepo SCSS package; deps consumed via @use/@forward, not JS imports — phantom-dep is a stable false positive here. ai
phantom-deps phantom-dep:@new-ui/colors AI (phantom-deps): Same monorepo SCSS pattern; stable false positive. ai
phantom-deps phantom-dep:@new-ui/effects AI (phantom-deps): Same monorepo SCSS pattern; stable false positive. ai
phantom-deps phantom-dep:@new-ui/spacings AI (phantom-deps): Same monorepo SCSS pattern; stable false positive. ai
phantom-deps phantom-dep:@new-ui/typography AI (phantom-deps): Same monorepo SCSS pattern; stable false positive. ai

Versions (showing 10 of 10)

Version Deps Published
0.3.6 5 / 5
0.3.5 5 / 5
0.3.4 5 / 6
0.3.3 5 / 6
0.3.2 5 / 3
0.3.1 5 / 3
0.3.0 5 / 3
0.2.6 5 / 3
0.2.5 5 / 3
0.2.4 5 / 3

v0.3.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.