← Home

@department-of-veterans-affairs/component-library

npm Repository

VA.gov component library. Includes React and web components.

6
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

powellkerryva_vsp_bot_npmmdbenjammlumetta_adhoctlei123zurbergramrtwellmottiezacharymorelbsmartin-epit-harrisonjamigibbsbeaugrantham-vatroettgeramyleademwilcorehumancompanion-vaediioterochrisgeorgecbonade-oddballrhasselle-oddballva-albershelene-mccarron

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from bot account to GitHub Actions is a documented CI/CD migration; SLSA attestation confirms integrity. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer cleanup consistent with org-level CI/CD migration for an established VA.gov package. ai
phantom-deps phantom-dep:react-transition-group AI (phantom-deps): react-transition-group is a declared runtime dependency used transitively; phantom-dep false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
56.4.0 6 / 7
56.3.0 6 / 7
54.2.0 6 / 7
54.1.2 6 / 7
54.1.1 6 / 7
54.1.0 6 / 7

v56.3.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.

v54.2.0

2 findings
HIGH Publisher changed: va_vsp_bot_npm → jamigibbs (on 2025-11-25) provenance

This version was published by a different npm account than previous versions on 2025-11-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v54.1.2

2 findings
HIGH Publisher changed: va_vsp_bot_npm → GitHub Actions (on 2025-11-19) provenance

This version was published by a different npm account than previous versions on 2025-11-19. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v54.1.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.

v54.1.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.