API maintenance and security review in one workspace. Know what your code depends on, what changed upstream, and what needs your attention.
Free. No card required.
Sign in with GitHub in your browser, or download for macOS and Windows.
From upstream change to a reviewable patch.Play it. Pause it. Explore each step.
A clear path from change to review.
Go from a repository full of dependencies to the specific code that deserves a closer look.
Actual interface · illustrative example data
Bring API usage, linked sources, and code locations into one inventory. See which integrations have changed and which findings need a closer look.
Explore API maintenanceFollow an integration into the files and functions that use it. Keep the source, call sites, and dependency context together as you investigate.
Explore dependency contextMove from a changed specification to affected code, security context, and a proposed patch. Inspect the evidence and checks before deciding what to ship.
See how you stay in controlCatalog API · /v2/items replaces /v1/products
Source evidence attachedcatalog.ts · listProducts() · line 18
Source evidence attachedclient.py · disabled TLS verification
Potential risk · review requiredProtectSUS builds your API integrations, verifies them, and keeps them working as APIs evolve.
Open the workspaceJust say what you need, like “send an SMS with Twilio when an order ships.” A team of agents finds the official docs and OpenAPI definition, builds the integration with timeouts, rate-limit handling, safe retries and cost limits, verifies every endpoint, and opens a draft pull request.
Check exposed credentials, unverified webhooks, missing 429 handling, unsafe retries, missing timeouts, and idempotency. Severity and confidence are scored separately. Export SARIF for GitHub code scanning.
Monitor provider documentation and changelogs, map changes to your call sites, and get repair pull requests with isolated checks before integrations break.
A suggestion is only useful when you can understand it. Inspect the source, the affected code, and the checks before deciding what to ship.
Download the desktop appTrace findings back to source changes and code locations. Review the diff in the same place.
Supported repairs include isolated checks. Missing coverage and unresolved behavior stay visible.
Start in manual mode. Choose your automation settings. Draft pull requests remain yours to review.
How it works, what it checks,
and where you stay in control.
Yes. ProtectSUS is free, with no subscription or payment card required. You can connect one active repository per account. Shared review capacity and usage limits apply. Feedback is optional; no promotion or public review is required.
ProtectSUS indexes connected GitHub repositories, identifies supported API usage, and monitors linked documentation and API specifications. Pushes and pull requests can trigger new assessments. Dynamic usage and incomplete coverage are reported explicitly.
No. Integrate and the integration audit never ask for provider keys. Generated pull requests reference environment variable names only, and you add the values in your own host's secret manager.
Manual review is the default. You can choose to prepare proposals or open verified draft pull requests for supported changes. Verification gates still apply, and ProtectSUS does not automatically merge pull requests.
For supported API contract migrations, ProtectSUS runs isolated checks against the precise patch and records the results. Contract replay is not a live-provider test or a guarantee of production correctness. The workspace shows what was checked and what still needs your review.
The maintenance workspace checks supported Python and JavaScript/TypeScript patterns, such as disabled TLS verification and dynamic shell execution. These are potential risks for you to review, not proof of an exploit or a complete security audit.
Download ProtectSUS for macOS or Windows, then sign in with GitHub in the desktop app. Install the ProtectSUS GitHub App on the repositories you want to connect. Repository access is checked before connecting. Initial indexing reads source without executing repository code.
Yes. Workspace settings include monitoring controls, automation modes, and limits for paid model work. Model calls require separate consent. You can pause monitoring and review the status of queued or running tasks.
Questions, a pilot for your team, or a walkthrough of your own repository? Book 30 minutes with the founders.
Open ProtectSUS in your browser, get it for Mac or Windows, or book a meeting and walk through it with us.
