The channels below route to the people who operate inspect.software directly.
Certification and commercial enquiries
Private repository audits, on-demand certification, monitoring, and enterprise reporting: mail@inspect.software
The available services and the rules they operate under are described on the certification & pricing page — including the rule that payment never changes a result.
Data corrections
A factual error in a published report — a mismatched package, stale evidence, a value that cannot be reproduced from its inputs — should be flagged with the repository's full name and the specific metric in question: mail@inspect.software
Confirmed data errors trigger a re-scan. Disagreements with the methodology itself are answered with the documented formula; well-argued cases inform the methodology roadmap.
Security
A vulnerability in inspect.software itself should be reported privately to the same address, marked security in the subject line, before any public disclosure. Reports are acknowledged and handled with priority.
Methodology questions
Most questions are already answered in public documentation:
- Methodology — the complete specification.
- Wiki — per-metric and per-category reference.
- FAQ — common questions, including corrections and independence.