@gravity-ui/gulp-utils
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@gravity-ui/readme-validator | AI (dependencies): Same-org first-party dependency from trusted gravity-ui publisher. | ai | |
| dependencies | unvetted-dep:to-through | AI (dependencies): to-through is a standard gulp/vinyl ecosystem package; stable false positive for this build-utility package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 6 / 15 | |
| 1.1.0 | 5 / 14 | |
| 1.0.3 | 5 / 14 | |
| 1.0.2 | 5 / 14 | |
| 1.0.1 | 5 / 14 | |
| 1.0.0 | 5 / 14 |
v1.1.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
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.