3 findingsStatic scanned
Runs OpenAI's Codex coding agent locally on your computer from the command line.
71.3M installs/moApache-2.0
Gumballwotersan Clean Code
gumballwotersan · Agent
Clean Code is a skill for Google Antigravity and a command line tool that tidies code written with AI assistants. It removes obvious and redundant comments, finds hardcoded credentials such as Supabase, Firebase, OpenAI, Anthropic and Stripe keys, moves them into a .env file with a public .env.example template and updates the .gitignore. It also detects which AI assistant or editor you are using and writes the matching rules file for it.
Written by ooruby from the README of @gumballwotersan/clean-code 1.4.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
AI assistants often leave obvious comments and hardcoded keys in code, and this removes both.
What you could do with it
- Strip the obvious comments an AI assistant added to a project while keeping directives like eslint-disable.
- Find an exposed Supabase or OpenAI key in your code, move it to a .env file and swap in an environment variable.
- Install a Git pre-commit hook so only the files staged for each commit are cleaned.
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 (scripts/clean_code.js:5)
- synchronous shell execution (scripts/clean_code.js:146)
- synchronous shell execution (scripts/clean_code.js:149)
- synchronous shell execution (scripts/clean_code.js:159)
- 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.
- Data handling disclosed
- finding
- no statement of what it reads, writes or sends (README.md)
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.
Corrected after a reading by hand on 2026-10-10
- No shipped credentials: the automated note “The scan matched 1 credential-shaped string in the published files. Location withheld pending disclosure to the maker.” was withdrawn. A sample Firebase configuration in a secret-detection test, with a key spelled from abc and 1234 and shorter than a real one.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Antigravity skill and CLI to strip unnecessary comments, sanitize hardcoded secrets (Supabase, Firebase, OpenAI, Stripe) into .env, and enforce clean code across AI workflows.
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 1.4.0, the file with digest sha512-NTq8baDz8vfBjWJKeEbWFOrz+TznErA6DH+9iDq/myW/lJNUAC0D0mD3ksoYrm6WDd5qPso6vAxGg2lGj3bxhw==, 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 @gumballwotersan/clean-code@1.4.0Pinned to 1.4.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
- @gumballwotersan/clean-code
- Version read
- 1.4.0
- 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/gumballwotersan-clean-code)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-07
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.