@carbon/colors@11.62.0
Colors for digital and software products using the Carbon Design System
AI Security Review
scanned 7h ago · by lpm-firewall-aiThe package’s postinstall starts telemetry without an opt-in, with collection gated to detected CI or container environments and disabled only through an environment setting. This warrants a warning for install-time telemetry; the inspected package entry points otherwise contain generated color data.
Decision evidence
public snapshot- The package runs `ibmtelemetry --config=telemetry.yml` from its postinstall script.
- The telemetry config sends metrics to `https://www-api.ibm.com/ibm-telemetry/v1/metrics` using a package project ID.
- The telemetry CLI starts a background process when it detects CI; telemetry is enabled unless `IBM_TELEMETRY_DISABLED=true`.
- The package entry points contain generated color constants.
- The telemetry dependency’s background process skips collection when CI is not detected.
- The telemetry config does not declare JavaScript function or token collection.
Source & flagged code
6 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThe package runs `ibmtelemetry --config=telemetry.yml` from its postinstall script.
package.jsonView on unpkg · L44Findings
Affected versions and remediation
This report applies to @carbon/colors@11.62.0.
See all versions of @carbon/colors for other recorded verdicts.
- Review the evidence and your use of @carbon/colors@11.62.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.