chalk-template
Terminal string styling with tagged template literals
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): eslint is a dev linting tool declared in dependencies by mistake; only referenced in config files, not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): eslint-plugin-import is a dev linting tool declared in dependencies by mistake; only referenced in config files, not a security risk. | ai | |
| phantom-deps | phantom-dep:@namics/eslint-config | AI (phantom-deps): ESLint config package misplaced in dependencies instead of devDependencies; only referenced in config files, not a security risk. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate transfer from qix to sindresorhus, both well-known chalk org maintainers. sindresorhus is a highly trusted publisher. | ai | |
| provenance | no-provenance | AI (provenance): Older publish predating widespread Sigstore adoption; informational only for this trusted package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.1.2 | 1 / 4 | |
| 1.1.0 | 1 / 4 | |
| 1.0.0 | 1 / 4 | |
| 0.5.0 | 1 / 4 | |
| 0.4.0 | 1 / 5 | |
| 0.3.1 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.0 | 1 / 4 | |
| 0.1.0 | 5 / 1 |
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
2 findingsThis version was published by a different npm account than previous versions on 2022-12-26. 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.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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 2022-01-17. This could indicate a legitimate maintainer transition or an account compromise.
v0.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.
v0.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.