← Home

@contrail/cli

VibeIQ's Contrail Platform CLI.

7
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

grant.hallbrian.lindauercfvibeiqbtosadopraterchris_vibeiqzileevamattvitellomazairajprashantvibeiqkartikisahuadamvibeiqzachsibert_vibeiqjaime-vibeiqmelba.lewisricardojsiscolrakeshvibeiqvadim-kozdanielurchuknwilde-vibeiqashutoshvibeiqraghuvibeiq

Keywords

clicontrail-cli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:node_modules/validate-color/lib/index.js AI (source-diff): Standard webpack bundle for validate-color color-validation library; no malicious indicators. ai
phantom-deps phantom-dep:aws-sdk AI (phantom-deps): aws-sdk is used via amazon-cognito-identity-js and config references; stable false positive for this CLI package. ai
dependencies unvetted-dep:json2csv AI (dependencies): Standard CSV export library; consistent with CLI data-loading functionality across versions. ai
dependencies unvetted-dep:pkg-install AI (dependencies): Used for plugin/package installation in CLI context; stable pattern across versions. ai
dependencies unvetted-dep:@contrail/loader AI (dependencies): First-party @contrail-scoped dependency bundled with the package; stable across versions. ai
dependencies unvetted-dep:@contrail/org-config-migration AI (dependencies): First-party @contrail-scoped dependency bundled with the package; stable across versions. ai
phantom-deps phantom-dep:command-line-usage AI (phantom-deps): command-line-usage referenced in config; stable false positive for this CLI package. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @contrail/cli is a scoped platform CLI with no relation to joi; Levenshtein match is coincidental. ai
phantom-deps phantom-dep:@typescript-eslint/eslint-plugin AI (phantom-deps): Dev/lint tooling referenced in config; stable false positive. ai
phantom-deps phantom-dep:@oclif/plugin-help AI (phantom-deps): oclif plugins are referenced in oclif config block, not direct imports; expected pattern. ai
phantom-deps phantom-dep:@oclif/plugin-autocomplete AI (phantom-deps): oclif plugins are referenced in oclif config block, not direct imports; expected pattern. ai
phantom-deps phantom-dep:esm AI (phantom-deps): esm is a loader referenced in config, not directly imported; stable false positive. ai
phantom-deps phantom-dep:arg AI (phantom-deps): arg referenced in config files; stable false positive for this CLI package. ai
phantom-deps phantom-dep:execa AI (phantom-deps): execa referenced in config files; stable false positive for this CLI package. ai

Versions (showing 7 of 7)

Version Deps Published
3.5.2 31 / 17
3.5.0 31 / 17
3.4.10 31 / 17
3.4.9 31 / 17
3.4.0 29 / 17
3.3.2 29 / 17
3.1.3 29 / 17

v3.5.2

2 findings
HIGH New obfuscated file: node_modules/validate-color/lib/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.4.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.