← Home

@digigov/css

npm
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

kpaptsironisvkefallinos.grnetthanasisk00sotirangelo

Keywords

design-systemcomponentsui-librarycomponentframeworkdesigncssui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Requires own package.json and tailwind.config.js via path.join(__dirname,...) — deterministic, not arbitrary module loading. ai
phantom-deps phantom-dep:publint AI (phantom-deps): publint is a CLI tool invoked via scripts, not imported; phantom-dep is a stable false positive here. ai
phantom-deps phantom-dep:@digigov/theme-default AI (phantom-deps): Same-org theme package used in config files; phantom-dep is a stable false positive. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped design-system CSS package; Levenshtein match to 'cors' is coincidental. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped design-system CSS package; Levenshtein match to 'qs' is coincidental. ai
phantom-deps phantom-dep:@fontsource/roboto AI (phantom-deps): @fontsource/roboto is a declared runtime dependency; referenced in config/build rather than direct JS imports — stable false positive for this CSS package. ai

Versions (showing 12 of 12)

Version Deps Published
2.3.0 1 / 13
2.2.3 1 / 13
2.2.1 1 / 13
2.2.0 1 / 13
2.1.1 1 / 13
2.1.0 1 / 13
2.0.14 8 / 16
2.0.11 8 / 16
2.0.9 8 / 16
2.0.7 8 / 16
2.0.4 8 / 16
2.0.3 8 / 16

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.3

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.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.

v2.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.

v2.0.14

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.

v2.0.11

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.

v2.0.9

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.

v2.0.7

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.

v2.0.4

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.

v2.0.3

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.