3 findingsStatic scanned
Runs OpenAI's Codex coding agent locally on your computer from the command line.
71.3M installs/moApache-2.0
Start Vibing Stacks
f1sc4ll · Agent
Start Vibing Stacks is a command line installer that sets up a shared AI engineering configuration in a repository: agents, skills, hooks, memories and quality gates. It writes the files each of Claude Code, Kimi Code, Grok and Cursor reads, keeps them in sync, and adapts to PHP, Node, Python and React Native projects. Hooks enforce a finish routine of a scoped commit, documentation updates and a docs commit. It suits teams that run more than one coding agent on one codebase.
Written by ooruby from the README of start-vibing-stacks 2.101.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Keeps the instructions, skills and hooks for Claude Code, Kimi and Grok, and the rules for Cursor, in step, so each agent follows the same finish routine.
What you could do with it
- Run the setup in an existing repository to add skills, agents, hooks and memories for your coding agents.
- Check what has drifted from the latest setup with a dry run, then apply the migration to update it.
- Start a React Native project and let the stack seed an Expo Router app with tabs, an auth panel or a blank app.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- python subprocess (stacks/_shared/skills/remove-ai-marks/scripts/container_meta.py:605)
- python subprocess (stacks/_shared/skills/remove-ai-marks/scripts/image_meta.py:192)
- python subprocess (stacks/_shared/skills/remove-ai-marks/scripts/image_meta.py:217)
- python subprocess (stacks/_shared/skills/remove-ai-marks/scripts/image_meta.py:432)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
- Licence and provenance
- finding
- no LICENCE file at the root (.)
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
AI-powered multi-stack dev workflow for Claude Code, Kimi Code, and Grok. Supports PHP, Node.js, Python, React Native / Expo and more.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 2.101.0, the file with digest sha512-L84wp8FpAqg3HfsNoqiLErnXNtq+94p/25oCH+3tiPSQxvQfb+hzfrq7B56GBeRqIxK4c6Yw1pNclNdTTjtTWg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y -p start-vibing-stacks@2.101.0 svsPinned to 2.101.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- start-vibing-stacks
- Version read
- 2.101.0
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/start-vibing-stacks)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-05
Similar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.