← Home

@kitschpatrol/stylelint-config

Stylelint configuration for @kitschpatrol/shared-config.

17
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

kitschpatrol

Keywords

stylelint-configstylelintclikscksc-stylelint

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@pinojs/json-colorizer AI (dependencies): Legitimate pino-ecosystem JSON colorizer utility; no malicious indicators. ai
provenance no-provenance AI (provenance): Established package with consistent publishing history; lack of provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:fs-extra AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:prettier AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:deepmerge AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:decircular AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:package-up AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:picocolors AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:cosmiconfig AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:execa AI (phantom-deps): Declared runtime dep used by CLI tooling; phantom-dep heuristic fires on config packages with indirect usage patterns. ai
phantom-deps phantom-dep:stylelint-config-html AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:@pinojs/json-colorizer AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:stylelint-config-standard AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:stylelint-config-clean-order AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:cosmiconfig-typescript-loader AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:json-stringify-pretty-compact AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:find-workspaces AI (phantom-deps): Declared runtime dep; stable false positive for this config package. ai
phantom-deps phantom-dep:yargs AI (phantom-deps): Declared runtime dep for CLI; stable false positive for this config package. ai

Versions (showing 17 of 17)

Version Deps Published
7.6.3 17 / 0
7.6.2 17 / 0
7.6.1 17 / 0
7.6.0 17 / 0
7.5.3 17 / 0
7.5.2 17 / 0
7.5.0 17 / 0
7.1.0 17 / 0
7.0.1 17 / 0
7.0.0 17 / 0
6.2.0 17 / 0
6.0.1 17 / 0
5.12.0 11 / 0
5.9.1 11 / 0
5.8.3 11 / 0
5.8.2 11 / 0
5.8.0 11 / 0

v7.6.3

1 finding
INFO No provenance attestation provenance

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

v7.6.2

1 finding
INFO No provenance attestation provenance

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

v7.6.1

1 finding
INFO No provenance attestation provenance

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

v7.6.0

1 finding
INFO No provenance attestation provenance

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

v7.5.3

1 finding
INFO No provenance attestation provenance

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

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

v7.1.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.

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

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

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

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

v5.12.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.

v5.9.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.

v5.8.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.

v5.8.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.

v5.8.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.