Least privilege
Request only the repository permissions required to perform the inspection.
Security
DeeNiX is designed to inspect useful evidence while minimizing the data and permissions it needs.
Core inspections use read-only GitHub repository access. Deenix does not need permission to push commits or merge changes to create a Health Passport.
We look for evidence that secrets are managed safely; we do not need the values of environment secrets to explain application health.
Health scoring maps to observed evidence. When a check cannot verify something, the result should reflect lower confidence instead of presenting an invented conclusion.
Any separate Rescue Service or engineering engagement is explicitly scoped and authorized. It is not implied by a standard inspection.
We can discuss your access, review, and data-handling requirements.
Contact us →Our operating principles
Software analysis should not require broad, permanent control of the systems being reviewed.
Request only the repository permissions required to perform the inspection.
A standard Health Passport inspection does not push, merge, deploy, or alter your application.
When evidence is missing, DeeNiX shows the gap instead of manufacturing certainty.
Any hands-on engineering work is separately scoped and approved before changes begin.
Security FAQ
No. Core inspections are designed around read-only access. Separate engineering work requires a distinct scope and authorization.
A repository inspection does not require your production secret values. Additional integrations, if enabled, should request only the access needed for their stated purpose.
The Passport identifies the missing evidence and lowers confidence rather than reporting an unsupported conclusion.