@2digits/prettier-config
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@2digits/constants | AI (dependencies): Same org scope as this package; internal dependency, not a supply chain risk. | ai | |
| dependencies | unvetted-dep:@prettier/plugin-oxc | AI (dependencies): Official @prettier org plugin; legitimate prettier ecosystem package. | ai | |
| dependencies | unvetted-dep:prettier-plugin-jsdoc | AI (dependencies): Well-known prettier plugin for JSDoc; stable ecosystem package. | ai | |
| provenance | no-provenance | AI (provenance): Org-scoped config package with long history; no provenance is consistent across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Config-only package with clear purpose from name; missing description is cosmetic, not a risk signal here. | ai | |
| phantom-deps | phantom-dep:local-pkg | AI (phantom-deps): Used in config files for plugin resolution, not a direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@prettier/plugin-oxc | AI (phantom-deps): Prettier config packages declare plugins as deps for consumers; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@2digits/constants | AI (phantom-deps): Same-org dependency; referenced in config files rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@prettier/plugin-xml | AI (phantom-deps): Prettier config packages declare plugins as deps for consumers; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-jsdoc | AI (phantom-deps): Prettier config packages declare plugins as deps for consumers; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-tailwindcss | AI (phantom-deps): Prettier config packages declare plugins as deps for consumers; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@ianvs/prettier-plugin-sort-imports | AI (phantom-deps): Prettier config packages declare plugins as deps for consumers; not directly imported by design. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 4.0.40 | 7 / 8 | |
| 4.0.39 | 7 / 8 | |
| 4.0.38 | 7 / 8 | |
| 4.0.37 | 7 / 8 | |
| 4.0.36 | 7 / 8 | |
| 4.0.35 | 7 / 8 | |
| 4.0.34 | 7 / 8 | |
| 4.0.33 | 7 / 8 | |
| 4.0.32 | 7 / 7 | |
| 4.0.31 | 7 / 7 | |
| 4.0.30 | 7 / 7 | |
| 4.0.29 | 7 / 7 | |
| 4.0.28 | 7 / 6 | |
| 4.0.27 | 7 / 6 | |
| 4.0.26 | 7 / 6 | |
| 4.0.25 | 7 / 6 | |
| 4.0.23 | 7 / 6 | |
| 4.0.22 | 7 / 6 | |
| 4.0.21 | 7 / 6 | |
| 4.0.20 | 7 / 6 | |
| 4.0.19 | 7 / 4 | |
| 4.0.18 | 7 / 4 | |
| 4.0.17 | 7 / 4 | |
| 4.0.16 | 7 / 4 | |
| 4.0.15 | 7 / 4 | |
| 4.0.14 | 7 / 4 | |
| 4.0.13 | 7 / 4 | |
| 4.0.12 | 7 / 4 | |
| 4.0.11 | 7 / 4 | |
| 4.0.10 | 7 / 4 | |
| 4.0.9 | 7 / 4 | |
| 4.0.7 | 7 / 4 | |
| 4.0.6 | 7 / 4 | |
| 4.0.5 | 7 / 4 | |
| 4.0.4 | 7 / 4 | |
| 4.0.3 | 7 / 4 | |
| 4.0.2 | 7 / 4 | |
| 4.0.1 | 7 / 4 | |
| 4.0.0 | 7 / 4 |
v4.0.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.