@marigold/icons
Marigold Icons
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual publish (sarahgm) to GitHub Actions CI with SLSA attestation is a legitimate supply-chain improvement. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): Long lines are SVG path data in a standard bundled CJS output; not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @marigold/* package in a design system; Levenshtein match to 'cors' is a false positive. | ai | |
| dependencies | unvetted-dep:@marigold/system | AI (dependencies): Internal sibling package from the same marigold-ui org; stable false positive for this package. | ai |
Versions (showing 68 of 68)
| Version | Deps | Published |
|---|---|---|
| 1.3.45 | 1 / 2 | |
| 1.3.44 | 1 / 2 | |
| 1.3.43 | 1 / 2 | |
| 1.3.42 | 1 / 2 | |
| 1.3.41 | 1 / 2 | |
| 1.3.40 | 1 / 2 | |
| 1.3.39 | 1 / 2 | |
| 1.3.38 | 1 / 2 | |
| 1.3.37 | 1 / 2 | |
| 1.3.36 | 1 / 2 | |
| 1.3.35 | 1 / 2 | |
| 1.3.34 | 1 / 2 | |
| 1.3.33 | 1 / 2 | |
| 1.3.32 | 1 / 2 | |
| 1.3.31 | 1 / 2 | |
| 1.3.30 | 1 / 2 | |
| 1.3.29 | 1 / 2 | |
| 1.3.28 | 1 / 2 | |
| 1.3.27 | 1 / 2 | |
| 1.3.26 | 1 / 2 | |
| 1.3.25 | 1 / 2 | |
| 1.3.24 | 1 / 2 | |
| 1.3.23 | 1 / 2 | |
| 1.3.22 | 1 / 2 | |
| 1.3.21 | 1 / 2 | |
| 1.3.20 | 1 / 2 | |
| 1.3.19 | 1 / 2 | |
| 1.3.18 | 1 / 2 | |
| 1.3.17 | 1 / 2 | |
| 1.3.15 | 1 / 2 | |
| 1.3.14 | 1 / 2 | |
| 1.3.13 | 1 / 2 | |
| 1.3.12 | 1 / 2 | |
| 1.3.11 | 1 / 2 | |
| 1.3.10 | 1 / 2 | |
| 1.3.9 | 1 / 2 | |
| 1.3.8 | 1 / 2 | |
| 1.3.7 | 1 / 2 | |
| 1.3.6 | 1 / 2 | |
| 1.3.5 | 1 / 2 | |
| 1.3.4 | 1 / 2 | |
| 1.3.3 | 1 / 2 | |
| 1.3.2 | 1 / 2 | |
| 1.3.1 | 1 / 2 | |
| 1.3.0 | 1 / 2 | |
| 1.2.69 | 1 / 2 | |
| 1.2.68 | 1 / 2 | |
| 1.2.67 | 1 / 2 | |
| 1.2.66 | 1 / 2 | |
| 1.2.65 | 1 / 2 | |
| 1.2.64 | 1 / 2 | |
| 1.2.63 | 1 / 2 | |
| 1.2.62 | 1 / 2 | |
| 1.2.61 | 1 / 2 | |
| 1.2.60 | 1 / 2 | |
| 1.2.59 | 1 / 2 | |
| 1.2.58 | 1 / 2 | |
| 1.2.57 | 1 / 2 | |
| 1.2.56 | 1 / 2 | |
| 1.2.55 | 1 / 2 | |
| 1.2.54 | 1 / 2 | |
| 1.2.53 | 1 / 2 | |
| 1.2.52 | 1 / 2 | |
| 1.2.51 | 1 / 2 | |
| 1.2.50 | 1 / 2 | |
| 1.2.49 | 1 / 2 | |
| 1.2.48 | 1 / 2 | |
| 1.2.47 | 1 / 2 |
v1.3.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sarahgm) than the most recent previously approved version (sebastiansebald) on 2025-04-11, but sarahgm 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.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.