@twilio/cli-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require used only to read package.json version field in require-install.js; not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:proxyquire | AI (phantom-deps): proxyquire is listed as a runtime dep but used in test/config context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@actions/github | AI (phantom-deps): Used in GitHub Actions scripts shipped in .github/scripts; not imported in main src. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): Referenced in oclif config, not directly imported; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.3.4 | 17 / 16 | |
| 8.3.3 | 17 / 16 | |
| 8.3.2 | 17 / 16 | |
| 8.3.1 | 17 / 16 | |
| 8.3.0 | 17 / 16 | |
| 8.2.5 | 17 / 16 | |
| 8.2.4 | 17 / 16 | |
| 8.2.3 | 17 / 16 | |
| 8.2.2 | 17 / 16 |
v8.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.