@coveo/cli-plugin-source
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@coveo/push-api-client | AI (phantom-deps): Same-org monorepo dep. | ai | |
| phantom-deps | phantom-dep:@oclif/core | AI (phantom-deps): oclif plugin framework dep used via CLI runtime. | ai | |
| phantom-deps | phantom-dep:@coveo/cli-commons | AI (phantom-deps): Same-org monorepo dep. | ai | |
| phantom-deps | phantom-dep:@coveo/platform-client | AI (phantom-deps): Same-org monorepo dep. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Config-referenced util dep, stable false positive. | ai | |
| phantom-deps | phantom-dep:ts-dedent | AI (phantom-deps): Config-referenced util dep, stable false positive. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-plugins | AI (phantom-deps): Declared in oclif config plugins array, not imported directly; stable pattern for oclif CLI plugins. | ai | |
| phantom-deps | phantom-dep:jsonschema | AI (phantom-deps): Used via config/schema validation, not direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): Declared in oclif config plugins array, not imported directly; stable pattern for oclif CLI plugins. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.3.11 | 9 / 16 | |
| 2.3.10 | 9 / 16 | |
| 2.3.9 | 9 / 16 | |
| 2.3.8 | 9 / 16 | |
| 2.3.7 | 9 / 16 | |
| 2.3.6 | 9 / 16 | |
| 2.3.5 | 9 / 16 | |
| 2.3.4 | 9 / 16 | |
| 2.3.3 | 9 / 16 | |
| 2.3.2 | 9 / 16 |
v2.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.