colors
get colors in your node.js console
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): Documented legitimate transition from marak to dabh (DABH is listed as contributor in package.json); dabh has a clean 7-package track record. Verdict generalizes to future versions by this publisher. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): dabh is a known, vetted contributor explicitly listed in package.json; the maintainer addition is a legitimate handoff, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy is consistent with the package's maturity and the documented maintainer transition; no malicious activity indicators accompany the resumed publishing. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): colors is a canonical, long-established package unrelated to cors. Levenshtein proximity is coincidental; not a typosquat. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by many years; absence is expected and not a risk signal for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is in an example file loading a known relative theme path; not in runtime library code and poses no real risk. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 0 / 2 | |
| 1.3.3 | 0 / 2 | |
| 1.3.2 | 0 / 2 | |
| 1.3.1 | 0 / 2 | |
| 1.3.0 | 0 / 2 | |
| 1.2.5 | 0 / 2 | |
| 1.2.4 | 0 / 2 | |
| 1.2.3 | 0 / 2 | |
| 1.2.2 | 0 / 0 | |
| 1.2.1 | 0 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.2 | 0 / 0 | |
| 1.1.1 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.3 | 0 / 0 | |
| 1.0.2 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 | |
| 0.6.2 | 0 / 0 | |
| 0.6.1 | 0 / 0 | |
| 0.6.0 | 0 / 0 | |
| 0.5.1 | 0 / 0 | |
| 0.5.0 | 0 / 0 | |
| 0.3.0 | 0 / 0 |
v1.3.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-12-10. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-22. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-05-20. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-05-05. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-30. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-30. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-12. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-10. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.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.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.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.
v0.3.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.