← Home

postcss-env-function

Use env() variables in CSS

17
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

constantscssenvironmentsenvsfunctionspostcsspostcss-pluginvariables

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/cli.mjs AI (source-diff): dist/cli.mjs is a Rollup-bundled CLI entry point; long lines are standard minification output, not obfuscation. This is expected for this package's build process. ai
source-diff net-exec-file:dist/cli.mjs AI (source-diff): The dynamic import() in cli.mjs loads user-specified local env files (importFrom feature). No actual network calls present. False positive for this package's documented functionality. ai
source-diff source-size-tripled AI (source-diff): Size increase is entirely explained by the new bundled CLI (dist/cli.mjs, 86KB), a Rollup bundle that inlines dependencies. Expected for this package. ai
dependencies unvetted-dep:postcss-value-parser AI (dependencies): postcss-value-parser is a well-known, widely-used PostCSS utility; its use here is expected and legitimate for a PostCSS plugin. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is intentional: the plugin loads user-specified JS environment files at runtime as a documented feature. Not a security risk in this context. ai
provenance no-provenance AI (provenance): Established package from a highly trusted publisher; lack of provenance attestation is not a meaningful risk signal here. ai
license uncommon-license:MIT-0 AI (license): MIT-0 is a recognized permissive license (MIT without attribution requirement); stable for this package from the csstools org. ai
phantom-deps phantom-dep:postcss-value-parser AI (phantom-deps): postcss-value-parser is a legitimate declared dependency in a monorepo context; phantom-dep flag is a false positive for this package. ai

Versions (showing 17 of 17)

Version Deps Published
8.0.0 1 / 0
7.0.0 1 / 0
6.0.0 1 / 1
5.0.1 1 / 0
5.0.0 1 / 0
4.0.6 1 / 0
4.0.5 1 / 2
4.0.4 1 / 2
4.0.3 1 / 2
4.0.2 1 / 8
4.0.1 1 / 8
4.0.0 1 / 9
3.0.0 2 / 8
2.0.2 2 / 10
2.0.1 2 / 10
2.0.0 2 / 10
1.0.0 2 / 9

v6.0.0

1 finding
LOW No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.0.6

1 finding
LOW No provenance attestation provenance

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

v4.0.5

1 finding
LOW No provenance attestation provenance

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

v4.0.4

1 finding
LOW No provenance attestation provenance

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

v4.0.3

3 findings
HIGH New obfuscated file: dist/cli.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/cli.mjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

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

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

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

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

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.