Radioupdater

C+ 71 completed
Other
unknown / json · tiny
17
Files
2,838
LOC
1
Frameworks
5
Languages

Pipeline State

completed
Run ID
#1546105
Phase
done
Progress
0%
Started
2026-04-16 23:47:03
Finished
2026-04-16 23:47:03
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
32.70
Framework unique
Isolation
Last stage change
2026-05-10 03:34:57
Deduplication group #47393
Member of a group with 256 similar repo(s) — canonical #1566037 view group →
Methodology: Repobility · https://repobility.com/research/state-of-ai-code-2026/

AI Prompt

Create a Chrome extension for Radiopaedia editors. This extension, called RadioUpdater, needs to add a "CiteItRight" button next to every reference textarea on an article or case edit page. When a user hovers over this button, it should check the reference formatting. The status button should display "Match," "Review," or "Error." If it shows "Review," hovering should preview suggested changes, and clicking should apply them. It must also support an "Undo" function to revert to the original reference. Please ensure the testing setup uses Vitest for utility functions like `sanitizeHTML` and `decodeHTML`.
chrome-extension javascript chrome-api radiopaedia dom-manipulation vitest web-app content-script
Generated by gemma4:latest

Catalog Information

Create a Chrome extension for Radiopaedia editors. This extension, called RadioUpdater, needs to add a "CiteItRight" button next to every reference textarea on an article or case edit page. When a user hovers over this button, it should check the reference formatting. The status button should display "Match," "Review," or "Error." If it shows "Review," hovering should preview suggested changes, and clicking should apply them. It must also support an "Undo" function to revert to the original refe

Tags

chrome-extension javascript chrome-api radiopaedia dom-manipulation vitest web-app content-script

Quality Score

C+
70.6/100
Structure
66
Code Quality
82
Documentation
36
Testing
75
Practices
76
Security
90
Dependencies
70

Strengths

  • CI/CD pipeline configured (github_actions)
  • Good test coverage (33% test-to-source ratio)
  • Good security practices — no major issues detected

Weaknesses

  • No LICENSE file — legal ambiguity for contributors
  • Potential hardcoded secrets in 1 files

Recommendations

  • Add a linter configuration to enforce code style consistency
  • Add a LICENSE file (MIT recommended for open source)
  • Move hardcoded secrets to environment variables or a secrets manager

Languages

json
73.8%
javascript
20.2%
markdown
2.9%
yaml
2.2%
css
1.0%

Frameworks

Vitest

Symbols

variable74
function25
constant4

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/1369875.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV