← Home

@alexlit/config-prettier

prettier config

23
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

alex-lit

Keywords

prettierconfig

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:prettier-plugin-sh AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:prettier-plugin-sql AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:@prettier/plugin-php AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:@prettier/plugin-pug AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:@prettier/plugin-xml AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:@prettier/plugin-ruby AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:prettier-plugin-eruby AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:prettier-plugin-jsdoc AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:prettier-plugin-solidity AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:prettier-plugin-sort-json AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:prettier-plugin-packagejson AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai
phantom-deps phantom-dep:prettier-plugin-tailwindcss AI (phantom-deps): Config package references plugins by name in config files, not via JS imports — expected pattern. ai

Versions (showing 23 of 23)

Version Deps Published
22.4.1 14 / 0
22.4.0 14 / 0
22.3.3 14 / 0
22.3.2 14 / 0
22.3.1 14 / 0
22.3.0 14 / 0
22.2.0 14 / 0
22.1.1 14 / 0
22.1.0 14 / 0
22.0.2 14 / 0
22.0.1 14 / 0
22.0.0 14 / 0
21.12.1 14 / 0
21.12.0 14 / 0
21.11.0 14 / 0
21.10.3 14 / 0
21.10.2 14 / 0
21.10.1 14 / 0
21.10.0 14 / 0
21.9.2 14 / 0
21.9.1 14 / 0
21.9.0 14 / 0
21.8.0 14 / 0

v22.4.1

1 finding
LOW No provenance attestation provenance

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

v22.3.3

1 finding
LOW No provenance attestation provenance

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

v22.3.2

1 finding
LOW No provenance attestation provenance

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

v22.3.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.

v22.3.0

1 finding
LOW No provenance attestation provenance

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

v22.2.0

1 finding
LOW No provenance attestation provenance

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

v22.1.1

1 finding
LOW No provenance attestation provenance

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

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

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

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

v22.0.0

1 finding
LOW No provenance attestation provenance

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

v21.12.1

1 finding
LOW No provenance attestation provenance

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

v21.12.0

1 finding
LOW No provenance attestation provenance

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

v21.11.0

1 finding
LOW No provenance attestation provenance

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

v21.10.3

1 finding
LOW No provenance attestation provenance

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

v21.10.2

1 finding
LOW No provenance attestation provenance

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

v21.10.1

1 finding
LOW No provenance attestation provenance

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

v21.10.0

1 finding
LOW No provenance attestation provenance

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

v21.9.2

1 finding
LOW No provenance attestation provenance

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

v21.9.1

1 finding
LOW No provenance attestation provenance

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

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

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