cmd-ts
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): Misplaced devDependency (lint config), not a malicious install-time dep. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 4 / 20 | |
| 0.14.3 | 4 / 20 | |
| 0.14.2 | 4 / 20 | |
| 0.14.1 | 4 / 20 | |
| 0.13.0 | 4 / 27 | |
| 0.12.1 | 4 / 27 | |
| 0.12.0 | 4 / 27 | |
| 0.11.0 | 4 / 27 | |
| 0.10.2 | 4 / 29 | |
| 0.10.1 | 4 / 29 | |
| 0.10.0 | 4 / 29 | |
| 0.9.0 | 4 / 29 | |
| 0.8.0 | 4 / 29 | |
| 0.7.0 | 4 / 29 | |
| 0.6.9 | 4 / 29 | |
| 0.6.8 | 4 / 29 | |
| 0.6.7 | 4 / 29 | |
| 0.6.6 | 4 / 29 | |
| 0.6.5 | 3 / 28 | |
| 0.6.4 | 3 / 28 | |
| 0.6.3 | 3 / 28 | |
| 0.6.2 | 2 / 27 | |
| 0.6.1 | 2 / 27 | |
| 0.6.0 | 2 / 27 | |
| 0.5.1 | 2 / 27 | |
| 0.5.0 | 2 / 27 | |
| 0.4.1 | 3 / 27 | |
| 0.4.0 | 4 / 26 | |
| 0.3.2 | 4 / 25 | |
| 0.3.1 | 4 / 25 | |
| 0.3.0 | 4 / 25 |
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.