You supply
- The website or application and permission to review it.
- For planned code review, a selected GitHub repository and version.
- Only where agreed, permitted access for specific runtime or server checks.
THE JOB, IN PLAIN ENGLISH
What you bring.
What you take away.
You get
- A list of issues, with file, page or system references where available.
- Recommended developer follow-up and a record of checks that could not run.
- A clear statement of the version, access and areas included in the review.
AGREE WHAT WILL BE REVIEWED
Useful findings.
Defined boundaries.
A website, a repository and a running server offer different evidence. Agree the access and checks before work begins.
Find website and application issues.
The website or application, the parts to review and permission to check them.
PROPOSED CHECK AREAS
- Page and response issues
- Security-related settings and response headers
- Areas that are blocked or outside the review
A developer issue list with affected pages, evidence and recommended follow-up.
A BRIEF A DEVELOPER CAN USE
The issue.
Its location. A next step.
Keep the relevant file, page or system reference with the finding. Explain what was observed and why it needs investigation.
A scoped review cannot certify that the whole system is secure. Unsupported checks and untested areas belong in the report.
KEEP THE DETAIL TOGETHER
Where the issue was found
The version and evidence
What could not be checked
BEFORE YOU START
A few useful
answers.
Does connecting GitHub check the entire codebase?
No. A connection provides authorised access. The chosen version, supported checks and included files define the review, and untested areas must stay explicit.
Will Fabric change or run repository code?
The planned code review is read only. Repository writes, deployments and executing untrusted project code are not part of this marketing flow.
Can runtime versions and dependencies be checked?
PHP versions, dependencies and related server checks are proposed scope. Any SSH or runtime access must be explicitly permitted and supported before it is used.
Does a report certify the system is secure?
No. A scoped review cannot guarantee that a whole website, application or codebase is secure. Findings need qualified human review and follow-up.
Want to hear when this audit is ready?
Join the waitlist and tell us the work you need help with.
Compare all audits