@redsift/products
Library providing hands-on implementation of components from Red Sift's Design System to fit their use cases.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@redsift/signal-logic | AI (dependencies): First-party @redsift scoped dependency; same org as the package under review. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Internal org package; publisher has 14 approved packages and no rejections — routine maintainer rotation. | ai | |
| provenance | no-provenance | AI (provenance): Established redsift org package; provenance absence is consistent across all 273 versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 12.5.4 | 6 / 48 | |
| 12.5.3 | 6 / 48 | |
| 12.5.2 | 6 / 48 | |
| 12.5.1 | 6 / 48 | |
| 12.5.0 | 6 / 48 | |
| 12.4.0 | 6 / 48 | |
| 12.3.0 | 6 / 48 | |
| 11.9.4 | 5 / 47 |
v12.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.3.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.
v11.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.