@redsift/ui-rs-hero
A customizable Hero unit.
1
Versions
MIT
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
martinhecherrahulpowar
Keywords
redsift-ui-componentredsift-uiredsift
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in gulpfile.js task loader — build tooling only, not shipped runtime code. | ai | |
| phantom-deps | phantom-dep:webcomponents.js | AI (phantom-deps): webcomponents.js is a declared runtime dep used via config/HTML, not directly imported in JS source — stable false positive for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 2 / 5 |
v0.4.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.