Interactive sample report
This fictional Passport shows the level of detail and transparency you can expect: what the repository proves, what Deenix infers, and what cannot be verified from code alone.
How to read this report
Directly supported by repository files, configuration, or dependency data.
A risk suggested by available evidence, but not proven without runtime or infrastructure access.
Outside the connected repository or missing enough evidence for a responsible conclusion.
Prioritized findings
Findings are ranked by likely business impact, strength of evidence, and the effort required to reduce the risk.
Why it matters Attackers may be able to use publicly documented weaknesses if the affected code paths are exposed.
package-lock.json · 3 direct dependencies · advisory match confirmedWhy it matters A service interruption could take longer to resolve if deployment and restore steps are unavailable to the wider team.
No runbook found · deployment workflow present · backup process not documentedWhy it matters A change can reach production even when the repository's existing tests fail or do not run.
.github/workflows/deploy.yml · deploy job has no test dependencyImportant limitations
Score transparency
The sample score summarizes weighted evidence across six categories. Missing evidence lowers confidence and can reduce a category score; it is never silently treated as a pass.
Ready to see your evidence?
Deenix uses read-only repository access and does not change or deploy your code.