Corrections

Every correction, retraction, and maintainer reply — dated, and left in place afterward.

The policy

A factual error is fixed the same day and logged here. A disputed interpretationgets the maintainer’s reply published verbatim beside the finding, with no grade change absent new evidence. A finding shown to be wrong is retracted, and the retraction stays visible.

Corrections are never quietly edited into the original text. The post is updated, and the change is recorded here with its date.

To report an error, open an issue on the repository or email corrections@plugrade.dev. Include the post, the claim, and what is wrong with it. Expect a reply within two working days.

Log

Nothing yet. The first audit publishes in August 2026; this page is live before it, so it can’t be described as an afterthought.

Known limits, standing

Some things are not errors but are worth knowing before you rely on a grade. Runtime-fetched code is outside what gets read. Remote MCP servers are opaque. Plugins with floating sources can change after they are scored. Token figures are estimates within roughly twenty percent. These are described in full on the methodology page.