@pi-r/gulp
Gulp task constructor for E-mc.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 65 versions and consistent repo; long gap plausible for a niche build-tool plugin. | ai | |
| dependencies | unvetted-dep:@e-mc/task | AI (dependencies): First-party @e-mc/* dep from same author/org; consistent across all versions of this package. | ai | |
| dependencies | unvetted-dep:@e-mc/types | AI (dependencies): First-party @e-mc/* dep from same author/org; consistent across all versions of this package. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): spawn() calls gulp/npx with user-configured args; expected behavior for a task runner wrapper. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Package is a Gulp task runner; child_process is required to spawn gulp/npx binaries — core functionality. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped gulp task package; name similarity to 'yup' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:gulp-cli | AI (phantom-deps): gulp-cli is a declared runtime dep used via CLI invocation, not directly imported. | ai | |
| phantom-deps | phantom-dep:gulp | AI (phantom-deps): gulp is a declared runtime dep used via config/CLI, not directly imported in source. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 5 / 0 | |
| 0.11.3 | 5 / 0 | |
| 0.11.2 | 5 / 0 | |
| 0.11.1 | 5 / 0 | |
| 0.11.0 | 5 / 0 | |
| 0.10.4 | 5 / 0 | |
| 0.10.3 | 5 / 0 | |
| 0.10.2 | 5 / 0 | |
| 0.10.1 | 5 / 0 | |
| 0.10.0 | 5 / 0 | |
| 0.9.5 | 5 / 0 | |
| 0.8.5 | 6 / 0 | |
| 0.7.6 | 6 / 0 | |
| 0.6.10 | 6 / 0 |
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.