Skip to content

rasuvaeff/* · 89 packages · data from Packagist and the tagged sources

PHP libraries, and how sure I am they work.

Victor Razuvaev, senior backend engineer: fifteen years of PHP, ten in ad-tech. The libraries cover deadlines, delivery, experiments and testing. This page shows the numbers behind them, including the one that turned out to be wrong.

A failing input, shrunk

The property says every integer from 0 to 10,000 stays below 100. The engine finds 3989, then tries smaller candidates until nothing smaller fails. This replays the real run, recorded from property-testing-core: seed 42, 39 trials.

3989first failing input
Property falsified after 0 successful run(s); seed=42
Original: value=3989
Shrunk: value=100 (9 shrink step(s), 39 trial(s))
Changed: value=3989 -> 100
Failure: 100 is not below 100

Every package has a mutation gate

A mutation gate fails the build when tests let too many deliberate bugs survive. Each dot is one package at its minMsi. Point at a dot for its name, click to open it.

 
Fig. 1. Mutation gate of 89 packages, from their latest tags. 20 require every mutant to be killed.

The metric lied, and this is by how much

Testo credits a test only with code named in its #[Covers], and Infection mutates only covered code. Code outside any #[Covers] produced no mutants, so reports said Not Covered: 0.

Fig. 2. Mutants across 75 packages. In json-ld alone the count went from 1,169 to 2,726 and the score from 97% to 41%. Only 4 of 75 packages met their own threshold. The thresholds were kept, and the tests caught up.

What the rest stands on

Fig. 3. Packages most often required by other rasuvaeff/* packages at their latest tags. context carries the request budget for 9 of them.

Worth opening

Chosen for what is hard to find elsewhere in PHP. Each opens as a manual page: synopsis, examples, see also, and the limits the package states itself under BUGS.

Testing
understudyTest doubles where the stub is a real method call. A rename is caught before the test runs.v1.1.1
property-testing-coreGenerates hundreds of inputs, shrinks the failing one, replays recorded failures from a corpus.v1.3.0
property-testing-openapiValid and invalid requests generated from an OpenAPI document, checked against the contract.v0.19.2
doc-execREADME code blocks run against the current code in CI.v0.1.0
Reliability under load
contextOne deadline and one cancellation signal through HTTP, DB, CLI and subprocesses.v0.3.0
yii3-outboxTransactional outbox for Yii3, with DB and ClickHouse backends.v1.8.0
yii3-idempotencySame key and body run the handler once. Keys are scoped per caller.v2.3.0
AI and security
yii3-mcpDomain methods become MCP tools, with a call budget, RBAC and an audit log.v5.0.0
pinned-http-clientResolve once, check every address, pin the connection.v1.0.1
Data and experiments
clickhouse-toolkitParameterized query builder, batch writer, DDL and partitions for ClickHouse.v1.12.0
yii3-ab-testingStateless hash assignment, explicit exposure tracking.v2.1.1

apropos

All 89 packages, searched the way apropos searches manual pages: by name and description.

  1. context(3)— Deadlines, cancellation and request-scoped values for PHP — one budget through HTTP calls, DB statement timeouts, CLI shutdown and subprocesses
  2. context-process(3)— Run external processes under a rasuvaeff/context budget: the timeout follows the deadline, cancellation stops the process (SIGTERM, then SIGKILL)

For agents

Every package ships an llms.txt API reference, and 40 ship an agent skill that the llm/skills Composer plugin syncs into .agents/skills/ on install. How it works.

Where they run

cska.in, a fan community rebuilt from a 20-year-old database, runs on 31 of the packages. ecosystem-sandbox puts 56 of them through one checkout. How the work is produced: workflow.