@types/gulp
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/* packages are loaded by convention, not direct import; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @types/gulp is the canonical DefinitelyTyped package for gulp; no relation to yup. | ai | |
| phantom-deps | phantom-dep:@types/vinyl-fs | AI (phantom-deps): Type-only peer dependency loaded by convention in DefinitelyTyped packages. | ai | |
| phantom-deps | phantom-dep:@types/undertaker | AI (phantom-deps): Type-only peer dependency loaded by convention in DefinitelyTyped packages. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.0.18 | 4 / 0 | |
| 4.0.17 | 4 / 0 | |
| 4.0.16 | 4 / 0 | |
| 4.0.15 | 3 / 0 | |
| 4.0.14 | 3 / 0 | |
| 4.0.13 | 3 / 0 | |
| 4.0.12 | 3 / 0 | |
| 4.0.11 | 3 / 0 | |
| 4.0.10 | 3 / 0 | |
| 4.0.9 | 3 / 0 | |
| 4.0.8 | 3 / 0 | |
| 4.0.7 | 3 / 0 | |
| 4.0.6 | 3 / 0 | |
| 4.0.5 | 3 / 0 | |
| 4.0.4 | 3 / 0 | |
| 4.0.3 | 3 / 0 | |
| 4.0.2 | 3 / 0 | |
| 4.0.1 | 3 / 0 | |
| 4.0.0 | 3 / 0 |
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.