Bibliostatus
C 61 completed
Other
containerized / r · tiny
38
Files
10,185
LOC
0
Frameworks
8
Languages
Pipeline State
completedRun ID
#710453Phase
doneProgress
0%Started
2026-04-15 00:28:28Finished
2026-04-15 00:28:28LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
38.80Framework unique
—Isolation
—Last stage change
2026-05-10 03:35:10Deduplication group #51636
Member of a group with 37 similar repo(s) — canonical #1208548 view group →
About: code-quality intelligence by Repobility · https://repobility.com
AI Prompt
Create a web application, similar to BiblioStatus, that displays the real-time opening status of public libraries on an interactive map. The app needs features like finding the nearest open library using GPS, searching libraries by name and auto-zooming, and filtering the map based on over 240 unique services. It should also include a service statistics dashboard with city filtering and a full daily schedule view for each location. Since the data is updated daily, please structure the project to handle data fetching, URL validation, and deployment, ideally using R for the core logic and ensuring a mobile-optimized layout with a dark mode toggle.
r web-app gis shiny map data-visualization sqlite github-actions scheduling
Generated by gemma4:latest
Catalog Information
Create a web application, similar to BiblioStatus, that displays the real-time opening status of public libraries on an interactive map. The app needs features like finding the nearest open library using GPS, searching libraries by name and auto-zooming, and filtering the map based on over 240 unique services. It should also include a service statistics dashboard with city filtering and a full daily schedule view for each location. Since the data is updated daily, please structure the project to
Tags
r web-app gis shiny map data-visualization sqlite github-actions scheduling
Quality Score
C
61.0/100
Structure
54
Code Quality
68
Documentation
61
Testing
15
Practices
78
Security
100
Dependencies
50
Strengths
- CI/CD pipeline configured (github_actions)
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
- Containerized deployment (Docker)
- Properly licensed project
Weaknesses
- No tests found — high risk of regressions
- 327 duplicate lines detected — consider DRY refactoring
- 2 'god files' with >500 LOC need decomposition
Recommendations
- Add a test suite — start with critical path integration tests
- Add a linter configuration to enforce code style consistency
Languages
Frameworks
None detected
Embed Badge
Add to your README:
