← The Index  /  security
Scored by model · 3 samples, median · No human review
Rank 123 of 173 · clearer than 28% of the index, 41% of security · Reviewed 2026-10-30

Patchclock

patchclock.com  ·  security
62
GRADE C
BAND 57–67

What their homepage claims

“PatchClock · EU Cyber Resilience Act compliance for PHP software vendors”

What that means

Compliance service for PHP software vendors to meet EU CRA requirements.

Verdict

Overall, the writing communicates a service to meet regulatory requirements, but relies on abstractions and domain jargon rather than naming a concrete product noun.

What to fix first

Ranked by what each change is worth on the composite — the gap to the next rung of the ladder times the dimension’s weight. Computed from the scores, not written by the model; the model’s sentence under each is the action.

  1. 1Clarity quick win 50 → 65+4.5

    Name a concrete service noun (e.g., “CRA compliance checks for PHP apps”) to make the offering unmistakable.

  2. 2Jargon-free quick win 65 → 80+3

    Limit or explain jargon, e.g., replace SBOM with a plain description of the artifact.

  3. 3Proof needs a fact 5 → 20+2.3

    Show a named customer or a concrete usage metric tied to a real organization.

All three together: 62 → 72. Every dimension one rung up: 72 (grade B). Ceiling is 95.

A plainer headline

Theirs
“PatchClock · EU Cyber Resilience Act compliance for PHP software vendors”
Index’s suggestion
“PatchClock helps PHP software vendors meet EU CRA requirements.”

Built only from facts already on the page — not the company’s words. Shown so the gap between what was written and what could have been written is concrete rather than a number.

Where the score comes from

Five dimensions on one ladder — 5 · 20 · 35 · 50 · 65 · 80 · 95 — weighted clarity 30%, specificity 20%, jargon 20%, proof 15%, call to action 15%. For each: the rung the page matched, the words that drove it, and what would reach the next rung. Full rubric →

Clarity30% 50

The page uses an abstract claim about “EU Cyber Resilience Act compliance” without naming a concrete product noun.

EU Cyber Resilience Act compliance

Next rungName a concrete service noun (e.g., “CRA compliance checks for PHP apps”) to make the offering unmistakable.

Specificity20% 95

The page anchors include multiple measurable items (24-hour, 72-hour, 14-day deadlines; 128 packages read).

✓ 128 packages read from composer.lock
Jargon-free20% 65

Contains industry terms like SBOM, CVE, Annex VII, and DISCLOSURE POLICY which may be opaque to newcomers.

SBOM and CVE alerts from composer.lock

Next rungLimit or explain jargon, e.g., replace SBOM with a plain description of the artifact.

Proof15% 5

No named customers or concrete adoption metrics are shown on the page.

Founding member offer: lock in your price

Next rungShow a named customer or a concrete usage metric tied to a real organization.

Call to action15% 95

Primary CTAs align with the promise (Run the free check, Reserve a place, Join the waitlist).

Run the free check

Evidence

PatchClock · EU Cyber Resilience Act compliance for PHP software vendorsShows the main headline used for evaluation.
Run the free checkClear CTA aligned with the claimed service.
SBOM and CVE alerts for Composer and npmDemonstrates specific features used as proof of capability.
What the scorer was given first 1,500 characters of the homepage text — check the quotes yourself
PatchClock · EU Cyber Resilience Act compliance for PHP software vendors
EU Cyber Resilience Act compliance
Your CRA clock , handled
For PHP software vendors, from Laravel apps to WordPress plugins and Shopware extensions. Know what the Cyber Resilience Act expects, keep your SBOM and support period current, and meet the 24-hour reporting deadline when it matters.
Run the free check
Founding offer
Talk to the founder
WORKS WITH
Composer
npm
GitHub
OSV.dev
CycloneDX
RFC 9116
ENISA reporting
Why PatchClock
Small software teams now carry the same legal duties as big vendors. The rules are clear on paper and vague in practice. PatchClock turns them into a short list of things to keep true, checks them for you and tells you when one slips.
Find your path
FOR DEVELOPERS
SBOM and CVE alerts from composer.lock
Connect a repo, get a CycloneDX SBOM for every release you tag, read within a minute of the push, and an alert when a locked version is affected.
Run the check →
FOR FOUNDERS
A plan for the day something is exploited
The 24h, 72h and 14-day reports drafted for you, plus the notice to your paying customers.
See the runbook →
FOR COMPLIANCE
Support period, policy and declaration
The technical documentation in Annex VII order, filled in with what PatchClock already knows, ready before 11 December 2027.
Why now →
● FREE CRA CHECK
Free CRA readiness check
We read your public pages and, if you add one, a public GitHub repository. You get a report on your security.txt , your disclosur

Terms struck

EU Cyber Resilience Act

How this compares

28%of the index scores lower
-6vs index mean (68)
-4vs security mean (66)
-7vs median (69)
64%of headline words survive
3×independently scored

Strongest: Specificity 95. Weakest: Proof 5. The 3 passes agreed within 9 points. The band 57–67 is where a re-score of this unchanged page would most likely land: on 42 dry re-scores (12 Oct 2026) the median move was 6 points and one in four moved more than 10. A grade only changes when a new score clears the boundary by 5.

Share this rating

Badges are issued to grades A and B. The share card for this page shows the headline with its jargon struck through; paste the URL anywhere that unfurls links.

Provenance

Scored from the live homepage on 2026-10-30 by gpt-5-nano, 3 independent passes, median taken. Page snapshot c2a0769634ea. Rubric 7329c240 (current; what it says). No person reviewed or edited this score. If the rubric and the score disagree, the rubric wins and the page is re-scored — not hand-corrected. Re-scored when the homepage text changes.