3 findingsStatic scanned
Runs OpenAI's Codex coding agent locally on your computer from the command line.
71.3M installs/moApache-2.0
Oversight Lint
rachelslurs · Agent
Oversight Lint checks the built Storybook components manifest, the file your coding agent reads through Storybook's MCP server, and fails the build when a component description never reached it, for example when extraction failed, the wrong docgen extractor ran or the JSDoc is missing. It does not run Storybook, so it needs a build from a recent Storybook with the components manifest enabled, which the MCP addon does for you; older versions are unsupported. It exits with distinct codes for a clean run, a failing rule and a run that could not start.
Written by ooruby from the README of oversight-lint 0.7.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
A drop in component documentation stops at CI, so your coding agent does not end up reading components that have no docs.
What you could do with it
- Add a CI step after building Storybook so a missing component description stops the build.
- Set the maximum number of warnings to zero so any new warning fails the run.
- State which docgen extractor your Storybook uses so the linter flags a manifest built with a different one.
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
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
Lint your Storybook MCP components manifest in CI. Fails the build when your agent would read missing or broken component docs.
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 0.7.1, the file with digest sha512-00572cS3+2t4/Ersp2KTx9ogorrKyO4HNNCnYQE+1lpTgEV5XS/Z70UHXuCYz7lcC7nwwirUXt0U+pDBa20KvQ==, 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 oversight-lint@0.7.1Pinned to 0.7.1, 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
- oversight-lint
- Version read
- 0.7.1
- 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/oversight-lint)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-08
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.