@marigold/system
Marigold System Library
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:cva | AI (dependencies): cva is the official rename/successor of class-variance-authority by the same author; low risk substitution. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI/CD, confirmed by SLSA provenance attestation. Stable for this package going forward. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): deepmerge is a declared runtime dependency; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-fast-compare | AI (phantom-deps): react-fast-compare is a declared runtime dependency; phantom-dep heuristic is a false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 17.5.0 | 6 / 7 | |
| 17.4.0 | 6 / 7 | |
| 17.2.1 | 6 / 7 | |
| 17.2.0 | 6 / 7 | |
| 17.1.0 | 6 / 7 | |
| 17.0.1 | 6 / 7 | |
| 17.0.0 | 6 / 7 | |
| 16.1.0 | 6 / 7 | |
| 16.0.1 | 6 / 7 | |
| 16.0.0 | 6 / 7 |
v17.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.