Example Digital
Tech stack currency is the weakest area (22/100).
- audited
- live sites
- 1 audited
maturity // section scores
- Tech stack currency22
- Delivery & deployment30
- Source control & code quality54
- Project management & agile44
- Security practices42
- Operations & support64
- Team shape91
- Sample projects93
Section weights: tech 15% · delivery 20% · source 15% · project 15% · security 10% · operations 10% · team 5% · sample 10%
If the team is already stretched, I can help.
NY8 can join as a private contractor for a specific upgrade, project or delivery bottleneck - no retainer, no obligation.
Why this needs to change
The weakest areas in this report: what staying as you are keeps costing, and what changes once it is fixed.
costing you now
Versions past end of life keep every vulnerability they already have and collect new ones, the newest libraries and hosting features are closed to you, and every year of waiting makes the upgrade bigger.
what changes
Security fixes start arriving on their own, upgrades stop being a project, and the stack stops being the reason a client says no.
costing you now
Releases depend on a person remembering the steps, so they happen rarely, late, and only when that person is free. Every release is a small gamble taken in front of the client.
what changes
A pipeline turns a release into a button: ship on a Tuesday afternoon, roll back in a minute, and let the pipeline hold the checklist instead of a person.
costing you now
Secrets in repositories, accounts without MFA and backups nobody has ever restored are the failures that end a client relationship in a single day.
what changes
Basic hygiene removes incidents that no insurance covers, and the security answers you can give in a tender become a reason to be chosen.
costing you now
Work that lives in chat and spreadsheets cannot be estimated, quoted or defended, so the team absorbs the difference as overtime.
what changes
A tracker and a rhythm make progress visible to the client, protect the team’s time, and turn quoting from a guess into a calculation.
Sample projects
Live sites the team handed over, audited by the Site Audit engine while this report was built.
92
The plan, as a checklist
Every failing check with something to do about it. Tick what is done and the score above the lists moves with you.
score with the fixes ticked
0 of 21 done
0%
Tick what you have done. Each tick counts that check as passed and the score moves with it.
Start here
the biggest gaps, most severe first0 / 8 doneDelivery & deployment
section score 300 / 3 doneSource control & code quality
section score 540 / 3 doneProject management & agile
section score 440 / 3 doneSecurity practices
section score 420 / 3 doneOperations & support
section score 640 / 1 doneEvery check
Open a section for its numbers, and each check's evidence and fix.
- in the stack
- 7
- past end of life
- 5
- out of support
- 1
- still supported
- 1
- upgrade plan
- partly
sources // version support dates from endoflife.date (cached for a day; an unreachable API leaves versions ungraded, never failed). Sample projects run through the same Site Audit engine as the rest of Tech Auditor. Everything else is scored from the answers given, and measures left as unknown stay unscored rather than counting as a failure. Weights: Tech stack currency 15% · Delivery & deployment 20% · Source control & code quality 15% · Project management & agile 15% · Security practices 10% · Operations & support 10% · Team shape 5% · Sample projects 10%. Release data checked .