@department-of-veterans-affairs/css-library
Department of Veterans Affairs stylesheets, tokens, and utilities
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): VA org package with documented team rotations; no malicious indicators. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine team churn for a government org; no takeover indicators. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal VA design system package; sparse metadata is consistent across versions and not indicative of spam/malware. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): rimraf is used in build scripts (clean-dist), not imported at runtime; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@uswds/uswds | AI (phantom-deps): Referenced in sass build script path, not imported as a module; expected pattern for CSS build packages. | ai | |
| phantom-deps | phantom-dep:@divriots/style-dictionary-to-figma | AI (phantom-deps): Design token tooling referenced in config, not directly imported; stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.32.0 | 7 / 2 | |
| 0.31.1 | 3 / 2 | |
| 0.31.0 | 3 / 2 | |
| 0.30.0 | 3 / 2 | |
| 0.29.1 | 3 / 2 | |
| 0.29.0 | 3 / 2 | |
| 0.28.0 | 3 / 2 | |
| 0.27.0 | 3 / 2 | |
| 0.26.0 | 3 / 2 | |
| 0.25.0 | 3 / 2 | |
| 0.24.0 | 3 / 2 | |
| 0.23.2 | 3 / 2 | |
| 0.23.1 | 3 / 2 | |
| 0.23.0 | 3 / 2 | |
| 0.22.2 | 3 / 2 |
v0.32.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jamigibbs) than the most recent previously approved version (powellkerry) on 2026-05-06, but jamigibbs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (powellkerry) than the most recent previously approved version (jamigibbs) on 2025-10-07, but powellkerry is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.25.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (va_vsp_bot_npm) than the most recent previously approved version (jamigibbs) on 2025-08-25, but va_vsp_bot_npm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (va_vsp_bot_npm) than the most recent previously approved version (jamigibbs) on 2025-08-18, but va_vsp_bot_npm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jamigibbs) than the most recent previously approved version (va_vsp_bot_npm) on 2025-07-31, but jamigibbs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.