Clean scanStatic scanned
Scaffolds OpenUI agent apps, mints Cloud API keys and turns component libraries into model prompts.
45.8k installs/moMIT
Create Vasvibe
bfibrianto · Template
create-vasvibe sets up a new project for the VasVibe development framework, with 20 specialised agents such as discovery, backend, frontend, security, DevOps and manual tester, plus prompts, skills and workflows. The same instructions are written out for several coding agent tools, including custom subagents and skills for Codex. You choose a work depth, from a fast single-agent prototype to a deep mode with full security and reliability work. Its quick start guide is in Indonesian.
Written by ooruby from the README of create-vasvibe 2.6.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your coding agents follow one planned, gated process with specialised roles, and each change is written down in the docs rather than made silently.
What you could do with it
- Create a project in deep mode for work on authentication or sensitive data, with security and reliability agents.
- Run the workspace setup to detect your coding tool and derive skills and MCP servers from your tech stack.
- Plan a project from a one-line idea, then build, test and release features through the gated phases.
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 (template/.opencode/skills/penetration-testing/references/automated-penetration-testing-framework.md:214)
- python subprocess (template/.claude/skills/penetration-testing/references/automated-penetration-testing-framework.md:214)
- python subprocess (template/.agents/skills/penetration-testing/references/automated-penetration-testing-framework.md:214)
- node child_process (src/git.mjs:4)
- 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
Scaffold a new project with VasVibe agents, prompts, skills, and workflows preconfigured (Codex, Claude, OpenCode, GitHub Copilot).
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.6.0, the file with digest sha512-VsXBSoCMYPu56O7soH65wBqR+l/FdmfHOJPwHEjCTkglsdvHtrPIuoT7LgzrLX8UINtvmYY6J+yJ6Z8omDhd1g==, 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 create-vasvibe@2.6.0Pinned to 2.6.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
- create-vasvibe
- Version read
- 2.6.0
- Resolved
- 2026-10-09
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/create-vasvibe)About this listing
- Kind
- Template
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-08
Similar templates
All templatesVerification 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.