Perpensa user guide
Use these guides to inventory your dependencies, understand findings, and choose a fix you can verify.
Get started
Section titled “Get started”| Your goal | Guide |
|---|---|
| Create an application and inspect the first scan | Your first scan |
| Understand scores, badges, and their limits | Understand results and scores |
| Go from a finding to a verified fix | Remediate a vulnerability |
A finding is an issue detected in a dependency. An update proposes a version change and may address several findings. Perpensa ranks this work; it does not open pull requests or apply version changes. You make the change in your repository, for example with Copy prompt and your coding agent, then a new scan confirms the result.
Find your way around the application
Section titled “Find your way around the application”Open the following pages in Perpensa. Paths shown here belong to the application, not this documentation site.
| Page | Purpose | Available introduction |
|---|---|---|
Applications (/app/applications) |
Configure environments, shared sources and local risk | Manage applications |
Overview (/app/overview) |
Organization overview | Overview reference |
Repositories (/app/repos) and repository details |
Repositories, tracked references, and scans | Your first scan |
Inventory (/app/inventory) |
Observed dependencies and versions | Your first scan |
Findings (/app/findings) and finding details |
Vulnerabilities and context | Understand results |
Update queue (/app/queue) and update details |
Ranked candidate updates | Remediate a vulnerability |
Digests (/app/digests) |
Summaries and notification delivery | Choose your email notifications |
Exports (/app/exports) |
Inventory exports, including SBOMs | Exporting results |
Settings (/app/settings) |
Organization, access, policies, and integrations | Choose your email notifications |
Before drawing a conclusion
Section titled “Before drawing a conclusion”Check the active organization, repository, scanned reference, and result date. A queued scan, incomplete inventory, active filter, or suppression may explain an empty list. The absence of findings does not guarantee the absence of vulnerabilities. Your role, plan, and integrations determine which data you can read and which actions you can take.
Scope and versions
Section titled “Scope and versions”This first edition covers the three workflows above. Detailed screen references and advanced features will be added progressively. Documentation is available in English only during this initial phase.
Applications, navigation and source-scoped results were verified on October 10, 2026; the remediation workflow on October 28, 2026. Examples named example/* and
their versions are fictional. Application scans use real repository contents and OSV responses. An unavailable
advisory service leaves coverage incomplete; it never supplies example findings.