@carbon/themes
Themes for applying color in the Carbon Design System
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Official IBM telemetry package, added consistently across Carbon monorepo packages. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files consistent with added build:types step generating .d.ts outputs; expected for this package's build pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Carbon Design System monorepo; CI-published with SLSA provenance; dormancy likely reflects release cadence, not takeover. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): IBM telemetry postinstall is a documented, stable pattern across all Carbon Design System packages. | ai | |
| phantom-deps | phantom-dep:@ibm/telemetry-js | AI (phantom-deps): @ibm/telemetry-js is used via CLI invocation in postinstall, not direct import; false positive for this package. | ai |
Versions (showing 84 of 84)
| Version | Deps | Published |
|---|---|---|
| 11.77.0 | 5 / 14 | |
| 11.76.1 | 5 / 14 | |
| 11.76.0 | 5 / 14 | |
| 11.75.0 | 5 / 14 | |
| 11.74.0 | 5 / 11 | |
| 11.73.0 | 5 / 11 | |
| 11.72.0 | 5 / 11 | |
| 11.71.0 | 5 / 11 | |
| 11.70.0 | 5 / 11 | |
| 11.69.0 | 5 / 11 | |
| 11.68.0 | 5 / 11 | |
| 11.67.0 | 5 / 11 | |
| 11.66.0 | 5 / 11 | |
| 11.65.0 | 5 / 11 | |
| 11.64.0 | 5 / 11 | |
| 11.63.0 | 5 / 11 | |
| 11.62.0 | 5 / 11 | |
| 11.61.0 | 5 / 11 | |
| 11.60.0 | 5 / 11 | |
| 11.59.0 | 5 / 11 | |
| 11.58.0 | 5 / 11 | |
| 11.57.0 | 5 / 11 | |
| 11.56.0 | 5 / 11 | |
| 11.55.0 | 5 / 11 | |
| 11.54.0 | 5 / 11 | |
| 11.53.0 | 5 / 11 | |
| 11.52.0 | 5 / 11 | |
| 11.50.0 | 5 / 11 | |
| 11.49.0 | 5 / 11 | |
| 11.48.2 | 5 / 11 | |
| 11.48.0 | 5 / 11 | |
| 11.47.0 | 5 / 11 | |
| 11.46.0 | 5 / 11 | |
| 11.45.0 | 5 / 11 | |
| 11.44.0 | 5 / 11 | |
| 11.43.0 | 5 / 11 | |
| 11.42.0 | 5 / 11 | |
| 11.41.1 | 5 / 11 | |
| 11.41.0 | 5 / 11 | |
| 11.39.0 | 5 / 11 | |
| 11.38.0 | 5 / 11 | |
| 11.37.1 | 5 / 11 | |
| 11.37.0 | 5 / 11 | |
| 11.35.0 | 5 / 11 | |
| 11.33.0 | 5 / 11 | |
| 11.32.0 | 4 / 11 | |
| 11.31.0 | 4 / 11 | |
| 11.30.0 | 4 / 11 | |
| 11.29.1 | 4 / 11 | |
| 11.29.0 | 4 / 11 | |
| 11.28.0 | 4 / 11 | |
| 11.27.1 | 4 / 11 | |
| 11.27.0 | 4 / 11 | |
| 11.26.1 | 4 / 11 | |
| 11.26.0 | 4 / 11 | |
| 11.25.0 | 4 / 11 | |
| 11.24.0 | 4 / 11 | |
| 11.23.0 | 4 / 11 | |
| 11.22.1 | 4 / 11 | |
| 11.22.0 | 4 / 11 | |
| 11.21.1 | 4 / 11 | |
| 11.21.0 | 4 / 11 | |
| 11.20.0 | 4 / 11 | |
| 11.19.0 | 4 / 11 | |
| 11.18.0 | 4 / 11 | |
| 11.17.0 | 4 / 11 | |
| 11.16.0 | 4 / 11 | |
| 11.15.0 | 4 / 11 | |
| 11.14.0 | 4 / 11 | |
| 11.13.0 | 4 / 11 | |
| 11.12.0 | 4 / 11 | |
| 11.11.0 | 4 / 11 | |
| 11.10.0 | 4 / 11 | |
| 11.9.0 | 4 / 11 | |
| 11.8.0 | 4 / 11 | |
| 11.7.0 | 4 / 11 | |
| 11.6.0 | 4 / 11 | |
| 11.5.0 | 4 / 11 | |
| 11.4.0 | 4 / 11 | |
| 11.3.0 | 4 / 11 | |
| 11.2.0 | 4 / 11 | |
| 11.1.0 | 4 / 11 | |
| 11.0.1 | 4 / 12 | |
| 11.0.0 | 4 / 12 |
v11.77.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.76.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.76.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.49.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.48.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.48.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.47.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.46.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.45.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.44.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.43.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.42.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.41.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.41.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.38.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.37.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.37.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.35.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.33.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.29.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.27.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.26.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v11.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.