Editorial and corrections policy
This policy explains how the site handles accountability, which sources count as evidence, how runnable claims are tested, and what happens when a reader reports an error.
Last substantively reviewed:
Review and accountability
Technical pages are reviewed for factual accuracy and reproducibility. A review date changes only after a substantive factual or methodological pass, not for a spelling-only edit. Readers can report errors using the correction channel below.
Source standard
Claims about CUID and CUID2 start with the implementation owners' repositories, source code, package releases, and documentation. Claims about UUIDs use the applicable RFC. Security guidance uses primary or recognized specialist sources such as OWASP. Secondary sources may help locate evidence but do not replace the source linked beside a material technical claim.
Testing and reproducibility
Runnable examples are limited to environments this repository can maintain. Before publication, the project runs its Node behavior tests, TypeScript checks, lint rules, and production build. Calculators expose formulas and assumptions; package-specific examples name the tested version. A format match is never presented as proof of origin, authenticity, uniqueness, or authorization.
Corrections
Reports should include the affected URL, the statement or result in question, reproduction steps when relevant, and a supporting source if available. Reports are checked against primary sources or reproducible tests. Substantiated errors are corrected, and affected page review dates are updated. No reply time is guaranteed.
Updates and scope
Content is revisited when an installed dependency, linked standard, or security recommendation materially changes. Pages state when a result is theoretical, implementation-specific, or outside the site's ability to verify. Examples that cannot be tested and maintained are removed instead of being presented as copy-paste guidance.
Automation and AI-assisted work
Automation and AI-assisted tools may be used to organize research, draft or revise text and code, and run routine checks. Generated output is not treated as a source. The project remains responsible for checking claims against cited material, reviewing code changes, running tests, and deciding what is published.
Commercial independence
Advertising does not determine identifier recommendations, comparisons, or test outcomes. CUID Generator is independent of the CUID and CUID2 maintainers. If sponsored or affiliate material is introduced in the future, it will be labeled where it appears.
Send a correction
Email info@cuidgenerator.com with the page URL and details. For a tool result, include the inputs you used and the result you expected.