@nysds/styles
CSS variables, styles, and themes for the New York State Design System
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@nysds/tokens | AI (phantom-deps): CSS-only package; @nysds/tokens is a sibling design-system dep consumed at build time, not via JS imports. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.19.3 | 1 / 1 | |
| 1.19.2 | 1 / 1 | |
| 1.19.1 | 1 / 1 | |
| 1.19.0 | 1 / 1 | |
| 1.18.3 | 1 / 1 | |
| 1.18.1 | 1 / 1 | |
| 1.18.0 | 1 / 1 | |
| 1.17.0 | 1 / 1 | |
| 1.16.1 | 1 / 1 | |
| 1.16.0 | 1 / 1 | |
| 1.15.1 | 1 / 1 | |
| 1.15.0 | 1 / 1 | |
| 1.14.0 | 1 / 1 | |
| 1.13.1 | 0 / 2 | |
| 1.13.0 | 0 / 1 | |
| 1.12.0 | 0 / 1 | |
| 1.11.4 | 0 / 1 | |
| 1.11.3 | 0 / 1 | |
| 1.11.2 | 0 / 1 | |
| 1.11.1 | 0 / 1 | |
| 1.11.0 | 0 / 1 | |
| 1.10.1 | 0 / 1 | |
| 1.10.0 | 0 / 1 | |
| 1.9.1 | 0 / 1 | |
| 1.9.0 | 0 / 1 | |
| 1.8.0 | 0 / 1 | |
| 1.7.0 | 0 / 1 | |
| 1.6.0 | 0 / 1 | |
| 1.5.3 | 0 / 1 | |
| 1.5.0 | 0 / 1 | |
| 1.4.0 | 0 / 1 | |
| 1.3.0 | 0 / 1 | |
| 1.2.0 | 0 / 1 | |
| 1.1.9 | 0 / 1 | |
| 1.1.8 | 0 / 1 | |
| 1.1.7 | 0 / 1 | |
| 1.1.6 | 0 / 1 | |
| 1.1.5 | 0 / 1 | |
| 1.1.4 | 0 / 1 | |
| 1.1.2 | 0 / 1 | |
| 1.1.1 | 0 / 3 | |
| 1.1.0 | 0 / 3 | |
| 1.0.0 | 0 / 3 |
v1.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsThis version was published by a different npm account (esteinborn) than the most recent previously approved version (plasticmind) on 2025-04-02. It has since remained available on npm for 471 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsThis version was published by a different npm account (esteinborn) than the most recent previously approved version (plasticmind) on 2025-03-24. It has since remained available on npm for 480 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.