← Home

@jobber/stylelint-config

npm

## Installing

4
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

timoteialbukonstantinramia-realchrismurrayjobber_servicesjc_weinrichdivyakrmichaelparadisjobbertaylorvnojericchernuka-jobberjmarvincameron.fscotttjobberstewart.b

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:style-search AI (phantom-deps): Config package; dependencies referenced in stylelint config, not code imports. ai
phantom-deps phantom-dep:stylelint-order AI (phantom-deps): Config package; dependencies referenced in stylelint config, not code imports. ai
phantom-deps phantom-dep:stylelint-config-standard AI (phantom-deps): Config package; dependencies referenced in stylelint config, not code imports. ai
phantom-deps phantom-dep:stylelint-config-css-modules AI (phantom-deps): Config package; dependencies referenced in stylelint config, not code imports. ai
phantom-deps phantom-dep:stylelint-declaration-block-no-ignored-properties AI (phantom-deps): Config package; dependencies referenced in stylelint config, not code imports. ai

Versions (showing 4 of 4)

Version Deps Published
0.7.3 5 / 2
0.7.2 5 / 2
0.7.1 5 / 2
0.7.0 5 / 2

v0.7.2

1 finding
LOW No provenance attestation provenance

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

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

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