@orintech/vectorci
v0.5.0
Published
GitHub-authenticated CLI for VectorCI setup and validation
Readme
VectorCI CLI
@orintech/vectorci is the supported product-side interface for VectorCI.
It contains one CLI and no MCP server. Products interact with VectorCI through
this pinned CLI, their own .vectorci.yml, public documentation, and the
provider-owned VectorCI GitHub check.
Install in a product repository
Node.js 24, Git, and GitHub CLI are required.
npm install --save-dev --save-exact @orintech/[email protected]
npx vectorci auth login
npx vectorci setup .Review the returned configuration and planDigest, then apply the exact plan:
npx vectorci setup . \
--apply \
--plan-digest <reviewed-sha256> \
--confirm WRITE_VECTORCI_CONFIG \
--open-appAfter the product repository commits and pushes .vectorci.yml, verify the
live provider result:
npx vectorci doctor .READY requires an accessible private repository matching origin, a valid
local configuration matching the GitHub default branch, and a successful
provider-owned VectorCI result on that exact branch head. The CLI accepts the
Check Run owned by GitHub App id 4500710, or—when a fine-grained product token
cannot read Checks—the VectorCI/provider status created by immutable App bot
user id 313620140. Give the selected-repository product credential Commit
statuses: read; no VectorCI repository permission is needed.
Security boundary
- Run the CLI from the exact current product Git repository.
- Use a product GitHub identity restricted to selected product repositories.
- The product identity must receive Not Found for
davidgrijalva-orin/VectorCI; the CLI fails closed if it cannot prove that denial. - The CLI refuses the VectorCI provider source repository, parent roots, and sibling repositories.
- The CLI never accepts, prints, stores, or writes a GitHub token.
- Setup creates only a missing
.vectorci.ymlafter a fresh digest and exact confirmation. It never commits or pushes product changes. - Product agents must not clone, list, inspect, execute, or modify the VectorCI provider repository.
Use npx vectorci docs, npx vectorci docs agents, or
npx vectorci docs --open for the version-matched guide.
Provider feedback is intentionally outside this package. A shared Codex skill will create reviewed bugs and stories in VectorCI's dedicated VectorGraph workspace after the Ticket Tracking CLI contract is released.
