@nysds/components
New York State's design system and code component library.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): lit-analyzer addition is a tooling dependency for Lit component analysis; consistent with the package's purpose. | ai | |
| dependencies | unvetted-dep:lit-analyzer | AI (dependencies): lit-analyzer is a well-known Lit framework static analysis tool; used as a build/lint script, not a runtime exploit vector. | ai | |
| phantom-deps | phantom-dep:lit-analyzer | AI (phantom-deps): Used as a CLI tool via 'lit-analyze' script, not imported directly; stable false positive. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): Newly added dep used in config/tooling context, not a direct import concern. | ai | |
| phantom-deps | phantom-dep:@figma/code-connect | AI (phantom-deps): Figma code-connect is a config/tooling dep; not imported at runtime. Stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/packages/nys-globalheader/src/nys-brand.logo.d.ts | AI (source-diff): Long line is an inline SVG string constant in a .d.ts file, not obfuscated code. | ai | |
| phantom-deps | phantom-dep:wc-datepicker | AI (phantom-deps): wc-datepicker is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.18.3 | 1 / 45 | |
| 1.18.1 | 1 / 45 | |
| 1.18.0 | 1 / 45 | |
| 1.17.0 | 1 / 45 | |
| 1.16.1 | 1 / 45 | |
| 1.16.0 | 1 / 45 | |
| 1.15.1 | 1 / 42 | |
| 1.15.0 | 1 / 41 | |
| 1.14.0 | 1 / 41 | |
| 1.13.1 | 1 / 38 | |
| 1.13.0 | 1 / 37 | |
| 1.12.0 | 0 / 37 | |
| 1.11.4 | 0 / 37 | |
| 1.11.3 | 0 / 37 | |
| 1.11.2 | 0 / 30 | |
| 1.11.1 | 0 / 30 | |
| 1.11.0 | 0 / 30 | |
| 1.10.1 | 3 / 28 | |
| 1.10.0 | 3 / 28 | |
| 1.9.1 | 3 / 28 | |
| 1.9.0 | 3 / 28 | |
| 1.8.0 | 2 / 28 | |
| 1.7.0 | 2 / 28 | |
| 1.6.0 | 2 / 27 | |
| 1.5.3 | 2 / 27 | |
| 1.5.2 | 2 / 27 | |
| 1.5.1 | 2 / 27 | |
| 1.5.0 | 2 / 27 | |
| 1.4.6 | 2 / 27 | |
| 1.4.5 | 2 / 27 | |
| 1.4.4 | 2 / 27 | |
| 1.4.3 | 2 / 27 | |
| 1.4.2 | 2 / 27 | |
| 1.4.1 | 2 / 27 | |
| 1.4.0 | 1 / 27 | |
| 1.3.0 | 1 / 27 | |
| 1.2.0 | 1 / 27 | |
| 1.1.9 | 1 / 33 | |
| 1.1.8 | 1 / 33 |
v1.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.