← Home

@kaliber/stylelint-plugin

npm

This Stylelint plugin enforces Kaliber's code conventions, helping maintain consistency across projects.

3
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

daveykropfeecolorjerryduijmkaliber-ownernhoenderopjanbrualbertkalibermvanbrakelit-traveleryoreljenkinsmdevalk1983guido.evertzensvroom-kalibertomharmsrinus.vhpgoddijnjvankralingen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@stylistic/stylelint-plugin AI (phantom-deps): Declared as dep and referenced in config files; not directly imported in JS but legitimately used as a stylelint plugin config reference. ai
phantom-deps phantom-dep:postcss-preset-env AI (phantom-deps): Config-file reference pattern; not a direct import by design for this plugin package. ai
phantom-deps phantom-dep:stylelint-use-nesting AI (phantom-deps): Config-file reference pattern; not a direct import by design for this plugin package. ai

Versions (showing 3 of 3)

Version Deps Published
2.0.0 11 / 0
1.0.4 8 / 0
1.0.3 8 / 0

v2.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: albertkaliber → tomharms (on 2026-05-29, known maintainer) provenance

This version was published by a different npm account (tomharms) than the most recent previously approved version (albertkaliber) on 2026-05-29, but tomharms 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.

v1.0.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: albertkaliber → guido.evertzen (on 2026-05-07, known maintainer) provenance

This version was published by a different npm account (guido.evertzen) than the most recent previously approved version (albertkaliber) on 2026-05-07, but guido.evertzen 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.

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