← Home

@massimo-cassandro/stylelint-config

npm Repository Homepage

my stylelint config

20
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

massimo-cassandro

Keywords

stylelint

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:stylelint-scss AI (phantom-deps): Stylelint configs reference plugins by string name in config objects, not JS imports — stable false positive for this package type. ai
phantom-deps phantom-dep:stylelint-config-standard AI (phantom-deps): Stylelint configs reference plugins by string name in config objects, not JS imports — stable false positive for this package type. ai
phantom-deps phantom-dep:@stylistic/stylelint-config AI (phantom-deps): Stylelint configs reference plugins by string name in config objects, not JS imports — stable false positive for this package type. ai
phantom-deps phantom-dep:@stylistic/stylelint-plugin AI (phantom-deps): Stylelint configs reference plugins by string name in config objects, not JS imports — stable false positive for this package type. ai
phantom-deps phantom-dep:stylelint-config-css-modules AI (phantom-deps): Stylelint configs reference plugins by string name in config objects, not JS imports — stable false positive for this package type. ai
phantom-deps phantom-dep:stylelint-config-recess-order AI (phantom-deps): Stylelint configs reference plugins by string name in config objects, not JS imports — stable false positive for this package type. ai
phantom-deps phantom-dep:stylelint-config-standard-scss AI (phantom-deps): Stylelint configs reference plugins by string name in config objects, not JS imports — stable false positive for this package type. ai

Versions (showing 20 of 20)

Version Deps Published
2.3.9 8 / 5
2.3.8 8 / 5
2.3.7 8 / 5
2.3.6 8 / 5
2.3.5 8 / 5
2.3.4 8 / 5
2.3.3 8 / 5
2.3.2 8 / 5
2.3.1 8 / 5
2.3.0 8 / 5
2.2.3 8 / 5
2.2.2 8 / 5
2.2.1 8 / 5
2.2.0 8 / 5
2.1.2 8 / 5
2.1.1 8 / 5
2.0.2 8 / 5
2.0.1 7 / 5
2.0.0 7 / 5
1.1.12 0 / 5

v2.3.9

1 finding
LOW No provenance attestation provenance

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

v2.3.8

1 finding
LOW No provenance attestation provenance

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

v2.3.7

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v2.3.4

1 finding
LOW No provenance attestation provenance

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

v2.3.3

1 finding
LOW No provenance attestation provenance

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

v2.3.2

1 finding
LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

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

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

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

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. 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. Consider requesting the maintainer enable provenance via CI/CD.

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

1 finding
LOW No provenance attestation provenance

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

v1.1.12

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.