@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, 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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo lockstep releases publish multiple packages within minutes; benign pattern. | ai | |
| 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 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 12.5.7 | 6 / 48 | |
| 12.5.5 | 6 / 48 | |
| 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.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (raul.lorenzo.redsift) than the most recent previously approved version (pierredupuis) on 2026-07-17, but raul.lorenzo.redsift is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.