Clean scanStatic scanned
Scaffolds OpenUI agent apps, mints Cloud API keys and turns component libraries into model prompts.
45.8k installs/moMIT
Azcodr
prosubodh · Template
Keeps AI-assisted development inside architecture rules you set. Its check command validates a repository's agent rules and skills, a pre-tool-use hook stops an agent adding code to a file already over a line limit until it is refactored, and a boundary engine runs in CI. A fresh scaffold adds skills for architecture, refactoring, compliance audits and product analysis, plus a glossary and a ledger of decision records. It is an early release.
Written by ooruby from the README of azcodr 2.7.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Architecture drifts when AI agents write code, so this turns the intended structure into rules the agent is checked against.
What you could do with it
- Run the check command on an existing repository to validate its agent rules and skills without scaffolding anything.
- Let the pre-tool-use hook block your agent from piling new logic into a file that is already over the line limit.
- Ask the architecture interview skill to settle the stack, frameworks and package manager before a project is bootstrapped.
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
- synchronous shell execution (README.md:234)
- node child_process (src/git.ts:1)
- synchronous shell execution (src/git.ts:34)
- node child_process (lib/git.d.ts:1)
- 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.
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
Architecture governance toolkit, with an optional starter (early release)
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.7.0, the file with digest sha512-BHPPDt81B2dghQlqHTQE+r7NU/c/VbQCCQuxBWD/LLfMd6ZSSt0L0Jeque3aS8zJMGBMtzNVQ03JcZycXvy0ew==, 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 azcodr@2.7.0Pinned to 2.7.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
- azcodr
- Version read
- 2.7.0
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/prosubodh/azcodr
- Commit
- 54dbaf55dc15
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
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/azcodr)About this listing
- Kind
- Template
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
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.