DEDUPEDAuthorization notice. Oc is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA developer or coding agent deciding whether to add an npm dependency to a project.
The problemThe npm registry page or raw JSON record is large, and the answer needed is a few fields.
The outcomeA short summary of the package's key fields that fits easily in an agent's context.
What you need first
- Node.js 20 or newer and npm
- A terminal the agent or you can run commands in
- Permission to install an npm package globally, or use npx instead
Steps
- Run
npm install -g @only-cli/oc - Run
oc npm pkg react(replace react with your package name) - If you need every field, run
oc raw
Prompt for your agent
Use the only-cli/oc repo: run `oc npm pkg <package>` for the target package name. Expect a short block with version, license, engines, and dependencies. Verify that the package name in the output matches the target before using the data.
Caveat. The npm shortcut keeps only the fields the project chose, so use Oc raw when a field is missing from the compact view.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page