Prepare your maintainer checklist
Mark only what you have actually prepared. This checklist runs in your browser. It does not request a scan or check your eligibility.
Your choices stay in this browser tab; they are not submitted to a scanner.
What the service offers
Anthropic describes OSS Scanner as free, periodic security scanning for accepted open-source projects. Participation is opt-in. The team validates core-maintainer involvement and reviews eligibility case by case, with attention to projects whose security matters to the wider ecosystem. This page cannot promise acceptance, coverage or a scan date.
Prepare the enrollment files
The official workflow uses a pull request to the OSS Scanner repository. A project directory contains project.yaml. The required information includes repo and primary_contact. Provide a Dockerfile path, or put a file named Dockerfile beside the YAML file and omit that path field.
The optional fields include homepage, threat_model, auto_ccs, pgp and disabled. The documented PGP option cannot be combined with CC recipients. Read the current repository instructions before preparing a real submission; do not put contact details, keys or repository contents into this checklist.
Build online, review offline
The build phase can use the network, but the audit environment runs offline. A build that succeeds only because a dependency is downloaded when a test starts is not ready for that environment. Install required dependencies and review tools during the build, then test the resulting container without network access. The upstream repository documents its validation helper, tools/validate.py; inspect the current instructions before running project code.
Keep a short record of the build revision, dependencies and a reproducible test command. Document expected failures and environment constraints. Passing a build check does not prove that the application is secure.
Example: a small parser library
Imagine a fictional image-parser project, PixelLedger. Its maintainer can describe which untrusted files it handles, where memory-safety mistakes would matter, and which inputs are intentionally unsupported. The Dockerfile installs the compiler and test fixtures. A network-disabled run then reveals a test that tries to download sample files. The maintainer includes the permitted fixtures in the build and repeats the offline check.
The useful outcome is a reproducible review environment and a clear trust boundary—not a statement that PixelLedger has passed a security audit. The maintainer also assigns time to reproduce incoming reports.
Triage reports before acting on them
Initial automated findings may not have human validation. Reproduce the described behavior, check the affected revision, and determine whether the stated preconditions are realistic. Keep unconfirmed reports separate from confirmed vulnerabilities and follow the service’s current disclosure guidance. Do not turn an automated severity label into a public claim without review.
For an opt-out, the upstream instructions describe setting disabled: true or removing your project through a pull request. This guide does not perform either action.
How this fits your development workflow
CodexTheme covers developer setup and troubleshooting. Scanner preparation is an adjacent maintainer task; installing a theme or following our setup guides does not enable OSS Scanner. Keep editor customization, repository permissions and security-review configuration separate.
Source and limits
Based on the official OSS Scanner overview and its linked enrollment repository, read on 10 October 2026. Service terms and eligibility can change. We have not enrolled a project or run an OSS Scanner audit for this guide. This independent guide is not affiliated with Anthropic.