← Home

@csstools/postcss-content-alt-text

npm Repository Homepage

Generate fallback values for content with alt text

12
Versions
MIT-0
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

jonathantnealalagunaromainmenke

Keywords

accessibilityaltcontentcsscsswgfallbackpostcss-pluginw3c

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@csstools/utilities AI (phantom-deps): Same-org @csstools package; phantom dep likely due to compiled dist output in monorepo. Stable false positive for this package. ai
phantom-deps phantom-dep:@csstools/css-tokenizer AI (phantom-deps): Same-org @csstools package; phantom dep likely due to compiled dist output in monorepo. Stable false positive for this package. ai
phantom-deps phantom-dep:@csstools/css-parser-algorithms AI (phantom-deps): Same-org @csstools package; phantom dep likely due to compiled dist output in monorepo. Stable false positive for this package. ai
phantom-deps phantom-dep:@csstools/postcss-progressive-custom-properties AI (phantom-deps): Same-org @csstools package; phantom dep likely due to compiled dist output in monorepo. Stable false positive for this package. ai
license uncommon-license:MIT-0 AI (license): MIT-0 is a well-known permissive license (MIT without attribution). Intentionally used by the csstools project. Not a security concern. ai

Versions (showing 12 of 12)

Version Deps Published
3.0.1 4 / 0
3.0.0 4 / 0
2.0.8 4 / 0
2.0.7 4 / 0
2.0.6 4 / 0
2.0.5 4 / 0
2.0.4 4 / 0
2.0.3 4 / 0
2.0.2 4 / 0
2.0.1 4 / 0
2.0.0 4 / 0
1.0.0 4 / 0

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.8

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

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

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

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

v1.0.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.