Originality checkpoints
AI investigates copyright, license, and reputational risk before launch.
Settings page redesign (AI-generated)
Pull request · PR #512 · askfairy.com
The code appears technically distinct, but the public settings page structure and warning copy are highly similar to an existing open-source product. Legal risk is unclear, but reputational risk is meaningful.
What was checked
Code copy risk
Code appears independently written; no repo match.
License risk
Dependencies are permissively licensed.
UI similarity risk
Page hierarchy + danger-zone structure mirror an OSS product.
Copy similarity risk
Warning copy is near-identical.
Reputation risk
Visible similarity on a public page could draw criticism.
Evidence quality
Strong UI/copy signals; legal threshold is a human call.
Sources searched (8)
Evidence found
Org policy applies: Public-facing UI requires originality review before launch· org policies · strong
Implementation code is technically distinct — no matching repository found18% similar· github · moderate
Settings page hierarchy and danger-zone layout closely mirror a well-known open-source product82% similar· competitor site · strong
Warning copy "This action cannot be undone…" is near-identical to that product91% similar· product page · strong
All dependencies are permissively licensed (MIT/Apache)· package license · strong
Unresolved questions
- Whether the detected similarity rises to a legal or reputational concern is a human judgment.
Recommended changes
- Rewrite the danger-zone and warning copy in your own voice
- Adjust the settings page hierarchy so it isn't a 1:1 mirror
- Request product + legal review before launch
Route to
Route to the recommended reviewers and hold launch until they decide.
Decision record DR-CHK-SETTINGS · evidence trail preserved