@vectoree/cli@0.1.17
Official Vectoree CLI — login, link, database, storage, Model Gateway, and Tool Hub
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged behavior is explained by documented CLI functions: authenticated requests go to the configured Vectoree API, and machine identification occurs as part of the explicit project-link flow. I found no install hook or unrelated command-output exfiltration behavior.
Decision evidence
public snapshot- The package has no install lifecycle scripts; its executable is the documented Vectoree CLI.
- API credentials are sent as Bearer tokens through requests to the configured Vectoree API origin.
- The machine ID and hostname are included when the user runs the project-link flow to create a CLI API key.
- App Auth snippets are generated and printed only when the user invokes the snippet command.
- The CLI entry point parses command-line arguments; no hidden install or startup task was identified.
- The apparent command-output and network patterns are consistent with CLI functionality and generated integration examples.
Source & flagged code
5 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
Findings
Affected versions and remediation
This report applies to @vectoree/cli@0.1.17.
See all versions of @vectoree/cli for other recorded verdicts.
- Review the evidence and your use of @vectoree/cli@0.1.17 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.