← Home

@hanzogui/linear-gradient

npm
9
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

artemis-primezeekay

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@hanzogui/core AI (phantom-deps): Same-org scoped dependency; likely used transitively by other @hanzogui packages. ai
phantom-deps phantom-dep:@hanzogui/native AI (phantom-deps): Same-org scoped dependency; likely used transitively by other @hanzogui packages. ai
phantom-deps phantom-dep:@hanzogui/stacks AI (phantom-deps): Same-org scoped dependency; likely used transitively by other @hanzogui packages. ai
bogus-package bogus-package AI (bogus-package): Org-scoped component library; missing metadata is expected for internal packages, not a spam/malware indicator. ai

Versions (showing 9 of 9)

Version Deps Published
7.0.0 3 / 4
3.0.2 3 / 4
3.0.1 3 / 4
3.0.0 3 / 4
2.0.8 3 / 4
2.0.7 3 / 4
2.0.5 3 / 4
2.0.4 3 / 4
2.0.0 3 / 4

v3.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.