gulp-plugin-prettier
Gulp plugin to format code with Prettier
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/through2 | AI (dependencies): @types/through2 is a TypeScript type definition package; benign dev-time artifact listed as runtime dep in this older project. | ai | |
| dependencies | unvetted-dep:@types/gulp-util | AI (dependencies): @types/gulp-util is a TypeScript type definition package; benign dev-time artifact listed as runtime dep in this older project. | ai | |
| phantom-deps | phantom-dep:@types/through2 | AI (phantom-deps): TypeScript @types packages are not directly imported at runtime; phantom-dep finding is expected for this package type. | ai | |
| phantom-deps | phantom-dep:@types/gulp-util | AI (phantom-deps): TypeScript @types packages are not directly imported at runtime; phantom-dep finding is expected for this package type. | ai | |
| provenance | no-provenance | AI (provenance): Package is 3197 days old, predating Sigstore provenance; absence is expected and not a security concern for this established package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 5 / 20 | |
| 2.0.1 | 5 / 19 | |
| 2.0.0 | 5 / 19 | |
| 1.1.0 | 2 / 16 | |
| 1.0.0 | 4 / 12 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.