@microsoft/fast-colors
A color utility for generating a range of colors from a single color
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): prettify.js is the standard Google Code Prettify syntax highlighter bundled by Istanbul in HTML coverage reports. Minified format is expected; this is a coverage artifact, not malicious obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from nirice to chrisdholt reflects a legitimate Microsoft internal team transition; chrisdholt has 603 approved packages and is a known Microsoft contributor. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Microsoft employees/bots (note -ms suffixes, microsoft1es bot). Consistent with normal Microsoft OSS team management for the FAST project. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Generic 'microsoft' account replaced by specific team member accounts — standard Microsoft OSS team transition, not a takeover signal. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package predating Sigstore provenance requirements; absence of attestation is expected for this version. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 5.3.1 | 0 / 8 | |
| 5.3.0 | 0 / 8 | |
| 5.2.0 | 0 / 8 | |
| 5.1.5 | 0 / 9 | |
| 5.1.4 | 0 / 9 | |
| 5.1.3 | 0 / 9 | |
| 5.1.2 | 0 / 9 | |
| 5.1.1 | 0 / 9 | |
| 5.1.0 | 0 / 10 | |
| 5.0.12 | 0 / 10 | |
| 5.0.11 | 0 / 10 | |
| 5.0.10 | 0 / 10 | |
| 5.0.9 | 0 / 10 | |
| 5.0.8 | 0 / 10 | |
| 5.0.7 | 0 / 10 | |
| 5.0.6 | 0 / 10 | |
| 5.0.5 | 0 / 10 | |
| 5.0.4 | 0 / 11 | |
| 5.0.3 | 0 / 11 | |
| 5.0.2 | 0 / 11 | |
| 5.0.1 | 0 / 11 | |
| 5.0.0 | 0 / 11 | |
| 4.2.1 | 0 / 11 | |
| 4.2.0 | 0 / 11 | |
| 4.1.2 | 0 / 11 | |
| 4.1.1 | 0 / 11 | |
| 4.1.0 | 0 / 11 | |
| 4.0.1 | 0 / 11 | |
| 4.0.0 | 0 / 11 | |
| 3.2.1 | 0 / 12 | |
| 3.2.0 | 0 / 12 | |
| 3.1.5 | 0 / 12 | |
| 3.1.4 | 0 / 12 | |
| 3.1.3 | 0 / 12 | |
| 3.1.2 | 0 / 12 | |
| 3.1.1 | 0 / 12 | |
| 3.1.0 | 0 / 12 | |
| 3.0.0 | 0 / 9 | |
| 2.2.1 | 0 / 9 | |
| 2.2.0 | 0 / 9 | |
| 2.1.0 | 0 / 7 | |
| 2.0.0 | 0 / 7 | |
| 1.9.2 | 0 / 7 | |
| 1.9.1 | 0 / 7 | |
| 1.9.0 | 0 / 7 | |
| 1.8.0 | 0 / 7 | |
| 1.7.0 | 0 / 7 | |
| 1.6.0 | 0 / 7 | |
| 1.5.0 | 0 / 7 | |
| 1.4.0 | 0 / 7 | |
| 1.2.0 | 0 / 7 | |
| 1.1.0 | 0 / 7 | |
| 1.0.4 | 0 / 7 |
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fastsvc.
[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 2021-10-31. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.3
2 findingsThis version was published by a different npm account than previous versions on 2021-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.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 2021-02-08. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.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 2020-07-14. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
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 2020-06-26. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.10
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 2020-06-09. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.9
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.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 2019-11-07. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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 2019-08-09. This could indicate a legitimate maintainer transition or an account compromise.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.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 2019-06-25. This could indicate a legitimate maintainer transition or an account compromise.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.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 2019-04-23. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.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.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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 2019-01-22. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.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-08-29. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.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-08-02. This could indicate a legitimate maintainer transition or an account compromise.
v1.9.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-07-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.9.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-07-14. This could indicate a legitimate maintainer transition or an account compromise.
v1.9.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-07-14. This could indicate a legitimate maintainer transition or an account compromise.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.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.
v1.2.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.
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.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.