Puts Claude in your terminal to understand your codebase, edit files and handle git workflows.
Codyswann Lisa
codyswann · App
Lisa is governance as code for AI-assisted software development, aimed at teams whose work is done by people, coding agents such as Claude Code and scheduled jobs alike. It applies one set of standards, workflows and quality gates to each repository and keeps them current as the package updates. Intake agents check incoming work, raise what they cannot resolve to a human, and run the rest through research, planning, implementation and verification.
Written by ooruby from the README of @codyswann/lisa 4.73.5.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
People, coding agents and scheduled jobs all build to the same standards, and changing those standards everywhere means updating one package.
What you could do with it
- Apply the same CI workflows, git hooks and project rules to each repository and upgrade them all by bumping one dependency.
- Let an intake agent screen a queue of ready work and send each item through research, planning, implementation and verification.
- Use only the linting, testing and TypeScript presets in a project without adopting the rest of Lisa.
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
- node child_process (typescript/copy-overwrite/scripts/check-threshold-ratchet.mjs:50)
- synchronous shell execution (typescript/copy-overwrite/scripts/check-threshold-ratchet.mjs:129)
- node child_process (typescript/copy-overwrite/scripts/check-verification-coverage.mjs:29)
- synchronous shell execution (typescript/copy-overwrite/scripts/check-verification-coverage.mjs:195)
- 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
Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects
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 4.73.5, the file with digest sha512-Ze7NJ6DxPhEInJ/SLDy6VedBQ9IFonoSeyidS4JDGoIZn/kBQfOZ319O9sjGAulaaPGfH0Fis6m/r3SXJIExXw==, 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 @codyswann/lisa@4.73.5 lisaPinned to 4.73.5, 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
- @codyswann/lisa
- Version read
- 4.73.5
- Resolved
- 2026-10-09
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/codyswanngt/lisa
- Commit
- 0e2b55ceb966
- 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/codyswann-lisa)About this listing
- Kind
- App
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
Similar apps
All appsGives your app one API for streaming from many AI model providers, with typed and validated tools.
Estimates how many tokens a text will use without loading a full tokeniser, from code or the shell.
Verification 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.