@types/prettier — Greenflagged

Stub TypeScript definitions entry for prettier, which provides its own types definitions

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@types/babel-types	AI (dependencies): Standard DefinitelyTyped cross-dependency for prettier's AST type definitions; expected and benign for this package.	ai	2026/04/22
phantom-deps	phantom-dep:@types/babel-types	AI (phantom-deps): @types/* packages are loaded by TypeScript convention, not direct imports; phantom-dep finding is a stable false positive for DefinitelyTyped packages.	ai	2026/04/22
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance on npm by years; absence is expected and not a risk signal for this well-established publisher.	ai	2026/04/22
bogus-package	bogus-package	AI (bogus-package): This is a legitimate @types stub package. Tiny payload, no README code, no repo URL, and no keywords are all expected for a stub that redirects to prettier's bundled types.	ai	2026/04/21
phantom-deps	phantom-dep:prettier	AI (phantom-deps): Stub package has no code to import dependencies; the prettier dep is a redirect by design, not a phantom dep in any meaningful sense.	ai	2026/04/21
dependencies	unvetted-dep:prettier	AI (dependencies): prettier is the canonical package this stub redirects to; the wildcard version constraint is standard for @types stub packages.	ai	2026/04/21

Versions (showing 65 of 65)

Version	Deps	Published
3.0.0	1 / 0	2023-07-29
2.7.3	0 / 0	2023-05-31
2.7.2	0 / 0	2022-12-20
2.7.1	0 / 0	2022-09-24
2.7.0	0 / 0	2022-08-04
2.6.4	0 / 0	2022-07-26
2.6.3	0 / 0	2022-05-28
2.6.2	0 / 0	2022-05-28
2.6.1	0 / 0	2022-05-12
2.6.0	0 / 0	2022-04-10
2.4.4	0 / 0	2022-02-09
2.4.3	0 / 0	2022-01-11
2.4.2	0 / 0	2021-11-13
2.4.1	0 / 0	2021-09-27
2.4.0	0 / 0	2021-09-25
2.3.2	0 / 0	2021-07-07
2.3.1	0 / 0	2021-07-01
2.3.0	0 / 0	2021-06-11
2.2.3	0 / 0	2021-03-15
2.2.2	0 / 0	2021-03-02
2.2.1	0 / 0	2021-02-13
2.2.0	0 / 0	2021-02-05
2.1.6	0 / 0	2020-12-23
2.1.5	0 / 0	2020-10-16
2.1.4	0 / 0	2020-10-16
2.1.3	0 / 0	2020-10-16
2.1.2	0 / 0	2020-10-10
2.1.1	0 / 0	2020-09-14
2.1.0	0 / 0	2020-08-27
2.0.2	0 / 0	2020-07-06
2.0.1	0 / 0	2020-05-21
2.0.0	0 / 0	2020-04-02
1.19.1	0 / 0	2020-03-22
1.19.0	0 / 0	2019-11-22
1.18.4	0 / 0	2019-11-19
1.18.3	0 / 0	2019-10-03
1.18.2	0 / 0	2019-08-12
1.18.1	0 / 0	2019-08-01
1.18.0	0 / 0	2019-07-19
1.16.4	0 / 0	2019-05-14
1.16.3	0 / 0	2019-04-19
1.16.2	0 / 0	2019-04-15
1.16.1	0 / 0	2019-02-13
1.16.0	0 / 0	2019-02-08
1.15.2	0 / 0	2018-11-28
1.15.1	0 / 0	2018-11-18
1.15.0	0 / 0	2018-11-16
1.13.2	0 / 0	2018-07-16
1.13.1	0 / 0	2018-06-12
1.13.0	0 / 0	2018-06-06
1.12.4	0 / 0	2018-05-24
1.12.3	0 / 0	2018-05-23
1.12.2	0 / 0	2018-05-11
1.12.1	0 / 0	2018-05-04
1.12.0	0 / 0	2018-04-13
1.10.0	0 / 0	2018-01-17
1.9.0	1 / 0	2017-12-11
1.8.1	1 / 0	2017-12-03
1.8.0	1 / 0	2017-11-09
1.7.2	1 / 0	2017-11-09
1.7.1	1 / 0	2017-10-19
1.7.0	1 / 0	2017-09-20
1.6.1	1 / 0	2017-09-06
1.6.0	1 / 0	2017-08-31
1.5.0	1 / 0	2017-07-22

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

v1.19.1

1 finding

LOW No provenance attestation provenance

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

v1.18.4

1 finding

LOW No provenance attestation provenance

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

v1.18.3

1 finding

LOW No provenance attestation provenance

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

v1.18.2

1 finding

LOW No provenance attestation provenance

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

v1.18.1

1 finding

LOW No provenance attestation provenance

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

v1.18.0

1 finding

LOW No provenance attestation provenance

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

v1.16.4

1 finding

LOW No provenance attestation provenance

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

v1.16.3

1 finding

LOW No provenance attestation provenance

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

v1.16.2

1 finding

LOW No provenance attestation provenance

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

v1.16.1

1 finding

LOW No provenance attestation provenance

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

v1.16.0

1 finding

LOW No provenance attestation provenance

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

v1.15.2

1 finding

LOW No provenance attestation provenance

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

v1.15.1

1 finding

LOW No provenance attestation provenance

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

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.13.2

1 finding

LOW No provenance attestation provenance

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

v1.13.1

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.4

1 finding

LOW No provenance attestation provenance

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

v1.12.3

1 finding

LOW No provenance attestation provenance

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

v1.12.2

1 finding

LOW No provenance attestation provenance

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

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

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

v1.10.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.

v1.9.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.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.

v1.6.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.

v1.5.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.