@types/gradient-string
TypeScript definitions for gradient-string
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/tinycolor2 | AI (phantom-deps): DefinitelyTyped packages routinely declare @types/* dependencies that are type-only and not directly imported; this is expected behavior for this package. | ai | |
| provenance | no-provenance | AI (provenance): DefinitelyTyped/@types packages are published via automated pipeline without Sigstore provenance; this is stable and expected for this publisher. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.1.6 | 1 / 0 | |
| 1.1.5 | 1 / 0 | |
| 1.1.4 | 1 / 0 | |
| 1.1.3 | 1 / 0 | |
| 1.1.2 | 1 / 0 | |
| 1.1.1 | 1 / 0 | |
| 1.1.0 | 1 / 0 |
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.