-
Notifications
You must be signed in to change notification settings - Fork 18
Expand file tree
/
Copy pathpubliccode.yml
More file actions
96 lines (93 loc) · 3.73 KB
/
publiccode.yml
File metadata and controls
96 lines (93 loc) · 3.73 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
---
publiccodeYmlVersion: 0.5.0
name: Quality-time
url: https://github.com/ICTU/quality-time.git
landingURL: https://github.com/ICTU/quality-time
logo: docs/src/_static/Quality-time.png
softwareVersion: 5.52.0
releaseDate: 2026-04-17
platforms:
- web
categories:
- agile-project-management
- application-development
- compliance-management
- data-collection
- it-development
- it-management
- it-security
organisation:
name: ICTU
uri: https://www.ictu.nl
fundedBy:
- name: ICTU
uri: https://www.ictu.nl
usedBy:
- ICTU
developmentStatus: stable
softwareType: standalone/web
description:
en:
shortDescription: Quality-time is an automated quality system for software
development and maintenance.
longDescription: >
*Quality-time* is a quality monitoring application for software
development and maintenance *Quality-time* collects measurement data
from sources such as GitLab, SonarQube, Jira, Azure DevOps, and OWASP
Dependency-Check, to provide an overview of the quality of software
products, processes, and projects. It does so by comparing measurement
data with metric targets and informing development teams about the
metrics that need improvement actions.
Technically, *Quality-time* consists of a React frontend, a Mongo database
server, and a number of backend components written in Python: a worker
component to collect measurement data from the sources, a worker component
to send notifications, an API-server for the frontend, and an API-server
for the worker components.
Users can add and configure reports, metrics, and sources (such as
SonarQube and Jira) in the frontend. The collector retrieves data from the
configured metric sources, determines the measurements, and stores them in
the database. The frontend calls the server to get the reports and the
measurements and presents them to the user.
*Quality-time* is developed by [ICTU](https://www.ictu.nl/en/about-us), an
impartial project organization within the government. ICTU's services
consist of the realization of projects and programs, giving advice, and
development of custom made software solutions. Driven by quality, with a
heart for the public task, not for profit.
documentation: https://quality-time.readthedocs.io/en/latest
apiDocumentation: https://quality-time.readthedocs.io/en/latest/api.html
features:
- Robust data collection (the collector should never fail, even in the
face of misconfigured or unavailable sources).
- Measurement history is kept in a database, allowing for time travel.
- Report configuration via the UI.
- Multiple reports in one Quality-time instance.
- LDAP-integration.
- Generic false-positive management.
- Metric tags can be used to summarize metrics with the same tag across
subjects, e.g. to summarize all security metrics.
- Export of reports to PDF, both via the UI as well as via the API.
- Notifications of events, such as metrics turning red, to Microsoft
Teams.
- Side-by-side comparison of measurements at different points in time.
- Integration with issue tracker (Jira only at the moment) to manage
actions and technical debt.
- Dark and light UI mode.
screenshots:
- screenshots/projects_dashboard_dark.png
- screenshots/projects_dashboard.png
legal:
license: Apache-2.0
mainCopyrightOwner: ICTU
dependsOn:
open:
- name: A container platform such as Docker or Kubernetes
maintenance:
type: community
contacts:
- name: Quality-time team
email: [email protected]
affiliation: ICTU
localisation:
localisationReady: false
availableLanguages:
- en