Reporting Errors
We maintain a Corrections Log on this page, listing every error fixed in the past 90 days. To report an issue:
- Navigate to the article in question.
- Click the Report an Error link at the article's footer.
- Describe the issue: the section, the broken command, and your environment (OS version, package versions).
Alternatively, email mail@zenonym.com or use our Contact form.
Verification Process
All reported errors go through this workflow:
| Step | Action | Timeline |
|---|---|---|
| 1 | Report received — logged with reporter name and environment | < 24 hours |
| 2 | Reproduced in test environment — confirm the issue exists | 24–72 hours |
| 3 | Fix applied — command updated, new screenshot added | 72–96 hours |
| 4 | Article updated — "Last Updated" date bumped, corrections log entry added | 96–120 hours |
Corrections Log
Last reviewed: September 2026
| Date | Article | Issue |
|---|---|---|
| September 2026 | Site-wide | Initial corrections policy published. |
Retractions
When a guide's core recommendation is found to be incorrect (e.g., a tool is deprecated, a threat model is invalidated), we add a prominent Notice box at the top of the article directing readers to a replacement guide. The original article remains accessible but is marked archived and removed from category listings.
Questions? Contact us. This policy is reviewed quarterly.