Code security review
Included with the Deep Scan and Security Care. Connect one GitHub repository with a read-only token and get a source-only security review in your report.
How to make the token
- On GitHub open Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token. Name it Lordevo code review, expiry 7 days is enough.
- Under Repository access choose Only select repositories and pick just this one repository.
- Under Repository permissions set Contents: Read-only (Metadata: Read-only is added automatically). Nothing else.
- Generate it, copy it (it starts with github_pat_) and paste it above. Use a token from an account that maintains the repository.
What happens
We download one commit (read-only), check it for committed secrets on our server, and then an AI model reviews the most security-relevant files; a different model tries to disprove each finding and we check every cited line exists. You get confirmed findings with severity, file, line and fix, plus leads to check. It is a single-pass, source-only review: we don't run your code, big repositories are only partly covered (the report says which files), and AI can miss issues. Reviews queue for capacity and can take from under an hour to a few days. Your token is stored encrypted and deleted when a one-off review finishes. More in How it works and our privacy notice.