Inspect access controls, dependencies and data handling
Choose an API, authorization flow, dependency set or configuration to inspect. Gryphon can read the code and report findings with file references.
Example: access to another customer’s order
An orders API supports several roles. Check that a user cannot retrieve another customer’s data.
- Trace authorization from the route to the data query.
- Confirm the finding with a reproducible example in a test environment.
- Prepare a fix and repeat the check across roles.
What you get
A report with code evidence, reproduction conditions and a proposed fix.
Prepare the project
Connect the repository in Desktop. Add role definitions and access rules if you have them. Configuration only needs the values relevant to the task; leave out secrets.
Read each finding
Look for the location in the code, conditions that trigger the issue and its consequences. Keep unconfirmed hypotheses separate from reproduced problems.
Test the fix
Reproduce the issue in a test environment, change the code and repeat the check. An AI review can help find vulnerabilities; it cannot guarantee that every vulnerability has been found.
Security
Our team observed an audit of a project with roughly 2500 files using about 130 glyphs. Usage depends on context, mode and actions. Project size does not imply every file was reviewed; fixes and repeat checks are separate tasks.
Try it on your own task
Open Web and describe the task. Connect Desktop for files and commands on your computer.