CRA Tool
Rule Violations
Allow users to easily track and prioritize important issues.
| Status | Open |
| Type | Closed-Source Collaborative |
| Eligible Courses | SEMI, PRAK/PROJ, Bachelor/Master Thesis |
| Scope | 5 ECTS - 30 ECTS |
| Use of Artificial Intelligence | Allowed |
| CLA Required? | Yes |
Summary
CRA Tool generates a large volume of "problems", including analysis warnings/errors, governance violations, vulnerabilities, license incompatibilities, version updates, and more. Managing this information can quickly become overwhelming, even for a single project.
As a proposed solution, users can define "rules" at project level to filter and prioritize relevant issues. Ideally, CRA Tool produces a prioritized, linear list of problems and provide guidance on how to resolve them.
Additional features can include:
- Labels, assignees, priorities, status tracking, and event logs
- Alerts and webhooks
- Integration with existing issue trackers like GitHub Issues or Jira
- Deduplication or grouping of similar problems
- The ability to create "teams" (e.g., "security team" or "compliance team") that automatically assigns relevant issues to specific groups
- ...
Related Tools:
- GitHub/GitLab Issues
- Sentry
- Rule Violations in ORT/ORT Workbench
- Rule Violations in DependencyTrack
Expected Tasks
- Create detailed GitHub issues
- Define an implementation timeline in the GitHub Project Roadmap
- Implement the solution and adapt your plan if necessary
- Write a brief project report (1-2 pages max)
Technologies
You should be familiar with the following programming languages:
- TypeScript
- Java
You should be familiar with the following frameworks/libraries:
- Next.js
- Spring Boot