@uswds/uswds
1
Versions
—
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
heymatthenryafeijoothisisdanoapetersen-gsa
Keywords
uiuswdscomponentslibraryopen sourceunited statesusau.s.governmentwebsites
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Used in build task to run tsc; standard build tooling for this package. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Spawns tsc for type-checking in gulp build task; not runtime code. | ai | |
| dependencies | unvetted-dep:receptor | AI (dependencies): receptor is a known USWDS event-handling utility; stable dependency for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.13.0 | 2 / 74 |
v3.13.0
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.