At Toolkit

D 53 completed
Other
unknown / javascript · tiny
22
Files
4,552
LOC
0
Frameworks
5
Languages

Pipeline State

completed
Run ID
#1535879
Phase
done
Progress
0%
Started
2026-04-16 16:51:35
Finished
2026-04-16 16:51:35
LLM tokens
0

Pipeline Metadata

Stage
Skipped
Decision
skip_scaffold_dup
Novelty
22.79
Framework unique
Isolation
Last stage change
2026-04-16 18:15:42
Deduplication group #47274
Member of a group with 3,548 similar repo(s) — canonical #1545452 view group →
Repobility (the analyzer behind this table) · https://repobility.com

AI Prompt

Create a comprehensive, offline-capable web-based toolkit for assistive technology. It needs to include six distinct handbooks covering various disabilities (Vision, Hearing, Mobility, Communication, Cognition, Self-Care), detailing tools and providers. Crucially, it must feature a needs assessment tool that allows side-by-side comparison across six international assessment frameworks: SETT, HAAT, ICF, WATI, MPT, and rATA. The entire application must adhere strictly to WCAG 2.1 AA accessibility standards, be keyboard navigable, and use semantic HTML5. Since it's a static PWA, all data should be stored locally using `localStorage`.
javascript html css pwa accessibility assistive-technology web-tool static-site healthcare education
Generated by gemma4:latest

Catalog Information

Create a comprehensive, offline-capable web-based toolkit for assistive technology. It needs to include six distinct handbooks covering various disabilities (Vision, Hearing, Mobility, Communication, Cognition, Self-Care), detailing tools and providers. Crucially, it must feature a needs assessment tool that allows side-by-side comparison across six international assessment frameworks: SETT, HAAT, ICF, WATI, MPT, and rATA. The entire application must adhere strictly to WCAG 2.1 AA accessibility

Tags

javascript html css pwa accessibility assistive-technology web-tool static-site healthcare education

Quality Score

D
52.7/100
Structure
44
Code Quality
62
Documentation
45
Testing
0
Practices
77
Security
100
Dependencies
50

Strengths

  • Consistent naming conventions (snake_case)
  • Good security practices — no major issues detected
  • Properly licensed project

Weaknesses

  • No tests found — high risk of regressions
  • No CI/CD configuration — manual testing and deployment
  • 426 duplicate lines detected — consider DRY refactoring
  • 3 'god files' with >500 LOC need decomposition

Recommendations

  • Add a test suite — start with critical path integration tests
  • Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
  • Add a linter configuration to enforce code style consistency

Languages

javascript
64.9%
css
24.2%
html
8.1%
markdown
2.2%
json
0.6%

Frameworks

None detected

Symbols

variable103
function43
constant7

API Endpoints (1)

Repobility · the analyzer behind every row · https://repobility.com
MethodPathHandlerFramework
Repobility · MCP-ready · https://repobility.com
GETtopicp.getExpress

Quality Timeline

1 quality score recorded.

View File Metrics
Want fix-PRs on findings? Install Repobility's GitHub App · github.com/apps/repobility-bot

Embed Badge

Add to your README:

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