@spectrum-web-components/icons-workflow
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 | no-provenance | AI (provenance): Established Adobe OSS monorepo package; provenance absence is consistent across all versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.12.2 | 2 / 6 | |
| 1.12.1 | 2 / 6 | |
| 1.12.0 | 2 / 6 | |
| 1.11.2 | 2 / 6 | |
| 1.11.1 | 2 / 6 | |
| 1.11.0 | 2 / 6 | |
| 1.10.0 | 2 / 6 | |
| 1.9.1 | 2 / 6 | |
| 1.1.0 | 2 / 9 |
v1.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
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 (rubenc) than the most recent previously approved version (rajrock38) on 2025-11-05, but rubenc 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.9.1
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 (rubenc) than the most recent previously approved version (rajrock38) on 2025-11-05, but rubenc 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.1.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.