Qupath Extension Qpsc

C 63 completed
Other
unknown / java · small
141
Files
43,659
LOC
0
Frameworks
5
Languages

Pipeline State

completed
Run ID
#390073
Phase
done
Progress
1%
Started
Finished
2026-04-13 01:31:02
LLM tokens
0

Pipeline Metadata

Stage
Skipped
Decision
skip_scaffold_dup
Novelty
47.67
Framework unique
Isolation
Last stage change
2026-04-16 18:15:42
Deduplication group #48155
Member of a group with 1 similar repo(s) — canonical #107945 view group →
Top concepts (2)
Project DescriptionBrowser Extension
If a scraper extracted this row, it came from Repobility (https://repobility.com)

AI Prompt

Create a Java extension for QuPath, similar to the QPSC system. This tool should allow users to control a microscope directly from within QuPath. Specifically, I need functionality for bounding box acquisition, where drawing a region automatically triggers high-resolution tiling and image acquisition. It should also support targeting existing annotations, automated stage control (including XY, Z, and rotation with safety checks), and multi-angle imaging for polarized light microscopy. Please structure the project to handle calibration workflows like background collection and polarizer calibration.
java qupath extension microscopy image-processing automation digital-pathology stage-control
Generated by gemma4:latest

Catalog Information

> Part of the QPSC (QuPath Scope Control) system > For complete installation instructions and system overview, see: https://github.com/uw-loci/QPSC

Description

> Part of the QPSC (QuPath Scope Control) system > For complete installation instructions and system overview, see: https://github.com/uw-loci/QPSC

Novelty

3/10

Tags

java qupath extension microscopy image-processing automation digital-pathology stage-control

Claude Models

claude-opus-4-6

Quality Score

C
63.2/100
Structure
62
Code Quality
42
Documentation
95
Testing
65
Practices
60
Security
75
Dependencies
50

Strengths

  • Well-documented README with substantial content
  • CI/CD pipeline configured (github_actions)
  • Consistent naming conventions (PascalCase)

Weaknesses

  • No LICENSE file \u2014 legal ambiguity for contributors
  • 6920 duplicate lines detected \u2014 consider DRY refactoring
  • 26 'god files' with >500 LOC need decomposition

Recommendations

  • Add a linter configuration to enforce code style consistency
  • Add a LICENSE file (MIT recommended for open source)
  • Address 376 TODO/FIXME items \u2014 consider tracking them as issues

Security & Health

106.6h
Tech Debt (D)
A
OWASP (100%)
PASS
Quality Gate
A
Risk (6)
Same scanner, your repo: https://repobility.com — Repobility
Unknown
License
7.0%
Duplication
Full Security Report AI Fix Prompts SARIF SBOM

Languages

java
93.7%
markdown
5.2%
yaml
0.6%
xml
0.2%
kotlin
0.2%

Frameworks

None detected

Concepts (2)

Analysis by Repobility (https://repobility.com) · MCP-ready
CategoryNameDescriptionConfidence
Repobility · code-quality intelligence · https://repobility.com
auto_descriptionProject Description![QuPath Version](https://qupath.github.io/) ![License](#license) ![Status](#)80%
auto_categoryBrowser Extensionbrowser-extension70%

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

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