tinygradient
Fast and small gradients manipulation, built on top of TinyColor
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:git.strangeplanet.fr | AI (email-domain): Author's own subdomain (strangeplanet.fr); not a public email provider. Low hijack risk for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump (v2) after long stable v1; consistent with intentional rewrite, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): Common for packages of this era; no provenance is typical and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@types/tinycolor2 | AI (phantom-deps): @types package ships type declarations for consumers; not directly imported at runtime. | ai |
v2.0.0
2 findingsMaintainer email '[email protected]' uses domain 'git.strangeplanet.fr' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
2 findingsMaintainer email '[email protected]' uses domain 'git.strangeplanet.fr' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.