Security Patches, Prepared for Review
When a new vulnerability affects your code, an agent prepares the patch, runs the tests, and hands it to your team for review.
Knowing About a Vulnerability Isn't Fixing It
Scanners report vulnerabilities faster than teams can patch them. Each one needs someone to check whether it applies, update the affected package or code, run the tests, and open a pull request. The queue of known issues grows while engineers work on everything else.
An Agent Does the Patch, a Person Approves It
An event from your security tooling, or a scheduled check, starts an agent. It checks whether your code is affected, applies the patched version or code change in an isolated environment, runs the tests, and opens a pull request. Your team reviews and merges it.
Patch PR waiting for review
Common Questions
What starts a patch?
An event your security tooling sends to Felan's webhook endpoint, a scheduled automation, or a person asking.
Does the agent see our production credentials?
Only if you give them to it. Each run happens in an isolated workspace, and Felan's own platform credentials, such as model keys, are filtered out of it. Give it only the repositories and access the patch needs.
Who approves the fix?
A person on your team, through a normal pull request review.
Can it run on our own infrastructure?
Yes. Use Felan's managed cloud, or run Felan on your own infrastructure with the Enterprise plan.
Related: Security docs, Dependency updates, Isolated by default.
Keep Your Attention for the Hard Problems
Start with one repo and one recurring task.