How do you scan a GitHub repository for vulnerabilities with Rafter? Connect only the repositories you are authorized to share, choose a branch and a Fast or Plus scan, review each finding against the code, make the fix, and scan again. Rafter is one security signal, not proof that a repository is safe. Its original AppSumo lifetime deal is sold out as checked on 23 October 2026; the prices still shown there describe a historical listing, not a purchase available today.
What Rafter does and where it fits
Rafter is a code-security tool with a GitHub-connected dashboard, scan reports and an optional CLI/API workflow. Its official getting-started guide describes selecting a repository and branch, running a Fast scan for common patterns or a Plus scan with deeper agent analysis, then reviewing findings by severity and file location. The vendor says it can inspect vulnerabilities, exposed secrets and risky dependencies. Treat these as product capabilities described by the vendor; no scanner catches every flaw, and this article does not claim that I ran a private repository test.
GitHub also provides its own code-security and secret-scanning tools. Before adding another service, compare what your repository already has enabled, who receives alerts, whether you need a second workflow, and what code access your organization permits. A repository scanner does not replace code review, dependency updates, access control, tests or monitoring after deployment.
Before you connect a repository
- Confirm authority and scope. Use a repository you own or are explicitly allowed to connect to a third-party scanner. For client code, check your contract and data-handling rules first.
- Review requested access. Rafter’s guide says to grant access to the repos you want scanned and manage that access from the dashboard. Inspect the exact GitHub authorization screen before approving it; a public blog cannot verify the permissions your account will see.
- Check data handling. Review Rafter’s privacy policy and terms with your team. These are vendor statements, not an independent audit of storage, deletion or security controls.
- Pick a low-risk first project. Start with a small repository and a named reviewer. Record the branch and commit so that you can tell whether a later scan covers the changed code.
Scan a GitHub repo with the Rafter dashboard
- Open the official Rafter dashboard, sign in, and connect GitHub only after reviewing the account permissions.
- Select the repository and branch. If the intended repository is absent, the vendor’s guide points to its Manage Access control; do not broaden access just to make a demo work.
- Choose Fast for an initial scan of common patterns. The vendor describes Plus as adding deeper agent analysis; check your current plan’s allowance before starting it.
- Open the completed report. Rafter groups findings as Critical, Warning and Note and shows file and line context. Record the scan date, commit and reviewer rather than copying a severity label into a ticket without context.
- Inspect the referenced code and reproduction path. Fix a confirmed issue in a reviewed change, then re-scan that branch. A dismissed false positive should have a reason and an owner.
Rafter’s setup page also describes API keys and CI/CD integration. Add a pipeline job only after you know its scan allowance, failure behavior and report access. Keep API keys in your CI secret store; do not paste them into a workflow file or a blog comment. The vendor’s instructions are the source for current setup details, which may change.
What to do when a scan flags a problem
| Finding | First review | Next step |
|---|---|---|
| Possible leaked key or token | Check whether it is real and active without publishing its value. | Revoke or rotate the credential first; then review usage and clean up the repository as needed. |
| Potential vulnerable dependency | Confirm the installed version, reachable use and available fix. | Upgrade or mitigate with tests, and re-scan the dependency tree. |
| Code pattern such as injection or weak authorization | Inspect the data flow and affected endpoint. | Make a code change with a reviewer and targeted test; verify behavior after deployment. |
| Likely false positive | Record why the path is not exploitable in this application. | Suppress only with a documented reason and revisit when code or exposure changes. |
For an exposed credential, GitHub’s official guidance says to revoke or rotate it first; history rewriting has side effects and does not substitute for invalidating the secret. Do not feed an actual secret value into a third-party AI prompt while asking for a fix. Rafter’s AI-ready explanation can support a developer, but someone still needs to review the proposed patch.
Rafter pricing and the AppSumo deal in October 2026
The exact Rafter AppSumo page says Sold out! and offers a notification form. It still displays this historical matrix:
| Former license tier | Displayed historical price | Fast scans/month | Sites |
|---|---|---|---|
| 1 | $39 | 15 | 10 |
| 2 | $99 | 50 | 100 |
| 3 | $199 | 150 | Unlimited |
The table’s Sites column concerns the separate live-site scan feature, not a count of GitHub repositories. These are not current checkout prices. Rafter also has a separate vendor pricing page for its present plans and scan credits. Check the live plan page and final checkout for your own account, and compare Fast versus Plus allowances before paying. Do not assume a former lifetime tier has the same limits as a present subscription or that a sold-out offer will return unchanged.
Who should use it?
Rafter may be useful for a small team that wants a second, readable scan report alongside GitHub’s native security features and has permission to let the service inspect the chosen repository. It may be a poor fit if your organization prohibits third-party code access, your existing GitHub alerts already cover the need, or nobody is assigned to investigate findings. For a Bangladesh-based agency handling client repos, document approval, data access, escalation and who will own the fixes before connecting any customer’s code.
If the repository supports a production WordPress site, code scanning and live-site hardening cover different risks. Our security and infrastructure services page describes help with deployment and recovery; it does not make a Rafter scan a substitute for operational controls.
Common questions
Can Rafter scan private GitHub repositories?
Rafter’s AppSumo listing includes public and private repositories, and its setup guide describes granting GitHub access. Whether your own repo is available depends on the permissions you approve and your organization’s policies.
Does a clean Rafter report prove the application is secure?
No. Scanner coverage, configuration and the specific commit matter. Combine automated findings with review, tests and production controls.
Does Rafter fix vulnerabilities automatically?
Its guide says findings include context that can be copied to a coding agent. A developer must still validate the issue, review the code change and re-test it.
Can I buy the Rafter AppSumo lifetime deal now?
Not on the original listing at this check. It is marked sold out on 23 October 2026. Recheck the exact page if you return later.
Sources checked: 23 October 2026. This is a documentation-based workflow and purchase-status review. It does not claim a 48-hour repository test, measured scan speed, alert delivery or a security audit of the vendor.