Report is generated at 28-06-2025-03-25-22 UTC
| # | ID | Team | 2025-Apr-06 | 2025-Apr-13 | 2025-Apr-20 | 2025-Apr-27 | 2025-May-04 | 2025-May-11 | 2025-May-18 | 2025-May-25 | 2025-Jun-01 | 2025-Jun-08 | 2025-Jun-15 | Errors Count Today |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | .github | qubership-devops |
9 | 9 | 9 | 13 | 13 | 13 | 13 | 13 | 13 | 13 | 13 | 13 |
| 2 | KubeMarine | qubership-infra administration, devops, helm, k8sstream, kubernetes |
10 | 10 | 14 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 3 | base-images-module-base | qubership-infra base-image |
12 | 12 | 14 | 14 | 14 | 14 | 13 | 13 | 13 | 13 | 13 | 13 |
| 4 | cassandra | ❌ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 |
| 5 | cassandra-exporter | qubership-infra |
12 | 12 | 14 | 14 | 10 | 9 | 10 | 10 | 10 | 10 | 10 | 10 |
| 6 | chart-releaser-action | qubership-devops |
0 | 0 | 0 | 0 | 0 | 0 | 15 | 15 | 14 | 14 | 14 | 14 |
| 7 | cla-storage | qubership-infra |
13 | 13 | 15 | 15 | 15 | 15 | 14 | 14 | 14 | 14 | 14 | 14 |
| 8 | gatekeeper-library | qubership-infra |
11 | 9 | 9 | 9 | 9 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 9 | get-package-ids | qubership-infra |
11 | 11 | 14 | 14 | 10 | 9 | 10 | 10 | 10 | 10 | 10 | 10 |
| 10 | k8s-conformance | qubership-infra |
13 | 13 | 15 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 |
| 11 | kafka | ❌ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 15 | 15 | 15 | 15 | 15 |
| 12 | keycloak | ❌ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 14 | 14 | 14 |
| 13 | microservice-restclient | qubership-infra |
11 | 11 | 14 | 14 | 10 | 9 | 10 | 10 | 10 | 10 | 10 | 10 |
| 14 | pg_hint_plan | qubership-infra |
11 | 11 | 14 | 14 | 10 | 9 | 10 | 10 | 10 | 10 | 10 | 10 |
| 15 | pgskipper-backup-daemon | qubership-infra |
12 | 12 | 15 | 11 | 11 | 11 | 10 | 10 | 10 | 10 | 10 | 10 |
| 16 | pgskipper-dbaas-adapter | qubership-infra |
12 | 12 | 14 | 13 | 13 | 13 | 12 | 12 | 12 | 12 | 12 | 12 |
| 17 | pgskipper-monitoring-agent | qubership-infra |
12 | 12 | 13 | 13 | 13 | 13 | 12 | 12 | 12 | 12 | 12 | 12 |
| 18 | pgskipper-operator | qubership-infra |
11 | 7 | 9 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | 5 | 5 |
| 19 | pgskipper-operator-core | qubership-infra |
12 | 12 | 15 | 15 | 15 | 15 | 14 | 14 | 14 | 14 | 14 | 14 |
| 20 | pgskipper-patroni | qubership-infra |
11 | 11 | 15 | 15 | 14 | 14 | 13 | 13 | 13 | 13 | 13 | 13 |
| 21 | pgskipper-pgbackrest-sidecar | qubership-infra |
11 | 11 | 14 | 14 | 14 | 14 | 13 | 13 | 13 | 13 | 13 | 13 |
| 22 | pgskipper-replication-controller | qubership-infra |
12 | 12 | 15 | 15 | 11 | 11 | 10 | 10 | 10 | 10 | 10 | 10 |
| 23 | pgskipper-upgrade | qubership-infra |
12 | 12 | 15 | 15 | 14 | 14 | 13 | 13 | 13 | 13 | 13 | 13 |
| 24 | postgres | ❌ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 15 | 15 | 15 | 15 | 15 |
| 25 | qubership-airflow | qubership-infra |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 |
| 26 | qubership-api-linter-service | qubership-apihub apihub |
0 | 9 | 9 | 7 | 7 | 7 | 6 | 6 | 6 | 6 | 6 | 6 |
| 27 | qubership-apihub | qubership-apihub apihub |
9 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 28 | qubership-apihub-agent | qubership-apihub apihub |
11 | 5 | 9 | 8 | 4 | 4 | 3 | 3 | 3 | 3 | 6 | 6 |
| 29 | qubership-apihub-api-data-model | qubership-apihub apihub, frontend |
11 | 11 | 15 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 30 | qubership-apihub-api-diff | qubership-apihub apihub, frontend |
10 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 31 | qubership-apihub-api-doc-viewer | qubership-apihub apihub, frontend |
10 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 32 | qubership-apihub-api-processor | qubership-apihub apihub, broadcast-pilot, frontend |
12 | 12 | 15 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 33 | qubership-apihub-api-unifier | qubership-apihub apihub, frontend |
10 | 10 | 14 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 34 | qubership-apihub-api-visitor | qubership-apihub apihub, frontend |
11 | 11 | 15 | 14 | 10 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 35 | qubership-apihub-apispec-view | qubership-apihub apihub, frontend |
11 | 11 | 15 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 36 | qubership-apihub-backend | qubership-apihub apihub, broadcast-pilot |
4 | 4 | 8 | 8 | 8 | 7 | 6 | 6 | 6 | 9 | 9 | 9 |
| 37 | qubership-apihub-build-task-consumer | qubership-apihub apihub, frontend |
10 | 10 | 14 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 38 | qubership-apihub-ci | qubership-apihub apihub |
11 | 11 | 15 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 39 | qubership-apihub-class-view | qubership-apihub apihub, frontend |
11 | 11 | 15 | 14 | 10 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 40 | qubership-apihub-compatibility-suites | qubership-apihub apihub, frontend |
10 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 41 | qubership-apihub-graphapi | qubership-apihub apihub, frontend |
9 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 42 | qubership-apihub-http-spec | qubership-apihub apihub, frontend |
10 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 43 | qubership-apihub-jest-chrome-in-docker-environment | qubership-apihub apihub, frontend |
9 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 44 | qubership-apihub-json-crawl | qubership-apihub apihub, frontend |
9 | 9 | 9 | 9 | 12 | 12 | 11 | 11 | 11 | 11 | 11 | 11 |
| 45 | qubership-apihub-nodejs-dev-image | qubership-apihub apihub, frontend |
11 | 11 | 15 | 14 | 12 | 12 | 10 | 10 | 10 | 10 | 10 | 10 |
| 46 | qubership-apihub-npm-gitflow | qubership-apihub apihub, frontend |
11 | 11 | 15 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 47 | qubership-apihub-postman-collections | qubership-apihub apihub |
9 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 48 | qubership-apihub-protobufjs-research | qubership-apihub apihub, frontend |
10 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 49 | qubership-apihub-rest-playground | qubership-apihub apihub, frontend |
11 | 11 | 15 | 14 | 10 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 50 | qubership-apihub-sniffer-agent | qubership-apihub apihub |
10 | 10 | 14 | 13 | 13 | 13 | 12 | 12 | 12 | 12 | 12 | 12 |
| 51 | qubership-apihub-test-service | qubership-apihub apihub |
11 | 11 | 14 | 9 | 11 | 11 | 10 | 10 | 10 | 10 | 10 | 10 |
| 52 | qubership-apihub-traffic-analyzer | qubership-apihub apihub |
11 | 11 | 15 | 14 | 14 | 14 | 13 | 13 | 13 | 13 | 13 | 13 |
| 53 | qubership-apihub-ui | qubership-apihub apihub, broadcast-pilot, frontend |
10 | 10 | 14 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 54 | qubership-apihub-ui-tests | qubership-apihub apihub, frontend |
10 | 10 | 14 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 55 | qubership-apihub-vscode | qubership-apihub apihub, frontend |
11 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 56 | qubership-av-scan-service | qubership-infra |
13 | 13 | 15 | 15 | 11 | 11 | 11 | 11 | 11 | 11 | 11 | 11 |
| 57 | qubership-backup-daemon | qubership-infra saqs |
11 | 11 | 14 | 14 | 10 | 9 | 9 | 6 | 6 | 6 | 6 | 6 |
| 58 | qubership-cloud-passport-cli | qubership-devops |
11 | 11 | 14 | 10 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 59 | qubership-colly | qubership-devops broadcast-pilot |
2 | 4 | 8 | 8 | 4 | 4 | 5 | 5 | 5 | 5 | 5 | 5 |
| 60 | qubership-consul | qubership-devops consul, saqs |
11 | 11 | 14 | 14 | 14 | 14 | 13 | 13 | 13 | 10 | 10 | 10 |
| 61 | qubership-consul-acl-configurator | qubership-devops consul, saqs |
11 | 11 | 14 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 62 | qubership-consul-backup-daemon | qubership-devops consul, saqs |
11 | 11 | 14 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 63 | qubership-core-base-images | qubership-core base-image, core |
7 | 7 | 8 | 7 | 7 | 7 | 6 | 6 | 6 | 6 | 6 | 6 |
| 64 | qubership-core-blue-green-state-monitor | qubership-core core, java, lib |
9 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 65 | qubership-core-blue-green-state-monitor-quarkus | qubership-core core, java, lib |
9 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 66 | qubership-core-bootstrap | qubership-core core |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 14 | 14 | 14 |
| 67 | qubership-core-config-server | qubership-core cloud-core, core, java, spring |
0 | 0 | 0 | 0 | 0 | 11 | 12 | 12 | 12 | 12 | 12 | 12 |
| 68 | qubership-core-context-propagation | qubership-core core, java, lib |
8 | 8 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 69 | qubership-core-context-propagation-quarkus | qubership-core core, java, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 70 | qubership-core-control-plane | qubership-core cloud-core, core, go, service-mesh |
9 | 9 | 9 | 14 | 11 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 71 | qubership-core-core-operator | qubership-core cloud-core, core, java, quarkus |
0 | 0 | 0 | 0 | 16 | 15 | 14 | 13 | 13 | 13 | 13 | 13 |
| 72 | qubership-core-dbaas-agent | qubership-core cloud-core, core, go |
13 | 13 | 15 | 15 | 15 | 14 | 14 | 14 | 13 | 13 | 13 | 13 |
| 73 | qubership-core-error-handling | qubership-core core, java, lib |
9 | 9 | 14 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 74 | qubership-core-facade-operator | qubership-core cloud-core, core, go |
0 | 0 | 0 | 0 | 16 | 16 | 13 | 13 | 13 | 13 | 13 | 13 |
| 75 | qubership-core-infra | qubership-core core |
12 | 12 | 16 | 16 | 16 | 16 | 15 | 15 | 15 | 16 | 16 | 16 |
| 76 | qubership-core-ingress-gateway | qubership-core cloud-core, core, envoy, service-mesh |
8 | 8 | 9 | 8 | 8 | 8 | 7 | 7 | 7 | 7 | 7 | 7 |
| 77 | qubership-core-junit-k8s-extension | qubership-core core, java, lib |
0 | 0 | 0 | 13 | 13 | 13 | 12 | 12 | 12 | 12 | 12 | 12 |
| 78 | qubership-core-lib-go | qubership-core core, go, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 79 | qubership-core-lib-go-actuator-common | qubership-core core, go, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 80 | qubership-core-lib-go-bg-kafka | qubership-core core, go, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 81 | qubership-core-lib-go-bg-state-monitor | qubership-core core, go, lib |
9 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 82 | qubership-core-lib-go-dbaas-arangodb-client | qubership-core core, go, lib |
8 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 83 | qubership-core-lib-go-dbaas-base-client | qubership-core core, go, lib |
9 | 9 | 9 | 14 | 12 | 12 | 11 | 11 | 11 | 11 | 11 | 11 |
| 84 | qubership-core-lib-go-dbaas-cassandra-client | qubership-core core, go, lib |
8 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 85 | qubership-core-lib-go-dbaas-clickhouse-client | qubership-core core, go, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 86 | qubership-core-lib-go-dbaas-mongo-client | qubership-core core, go, lib |
8 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 87 | qubership-core-lib-go-dbaas-opensearch-client | qubership-core core, go, lib |
8 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 88 | qubership-core-lib-go-dbaas-postgres-client | qubership-core core, go, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 89 | qubership-core-lib-go-error-handling | qubership-core core, go, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 90 | qubership-core-lib-go-fiber-server-utils | qubership-core core, go, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 91 | qubership-core-lib-go-maas-bg-segmentio | qubership-core core, go, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 92 | qubership-core-lib-go-maas-client | qubership-core core, go, lib |
9 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 93 | qubership-core-lib-go-maas-core | qubership-core core, go, lib |
8 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 94 | qubership-core-lib-go-maas-segmentio | qubership-core core, go, lib |
8 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 95 | qubership-core-lib-go-paas-mediation-client | qubership-core core, go, lib |
10 | 10 | 15 | 15 | 15 | 15 | 14 | 14 | 14 | 14 | 14 | 14 |
| 96 | qubership-core-lib-go-rest-utils | qubership-core core, go, lib |
8 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 97 | qubership-core-lib-go-stomp-websocket | qubership-core core, go, lib |
8 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 98 | qubership-core-maas-agent | qubership-core cloud-core, core, go |
11 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 99 | qubership-core-microservice-dependencies | qubership-core core, java, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 100 | qubership-core-microservice-framework | qubership-core core, java, lib |
9 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 101 | qubership-core-microservice-framework-extensions | qubership-core core, java, lib |
9 | 9 | 14 | 11 | 11 | 11 | 10 | 10 | 10 | 10 | 10 | 10 |
| 102 | qubership-core-mongo-evolution | qubership-core core, java, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 103 | qubership-core-paas-mediation | qubership-core cloud-core, core, go |
0 | 0 | 0 | 0 | 14 | 13 | 12 | 12 | 12 | 12 | 12 | 12 |
| 104 | qubership-core-process-orchestrator | qubership-core core, java, lib |
8 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 105 | qubership-core-quarkus-extensions | qubership-core core, java, lib |
9 | 9 | 14 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 106 | qubership-core-rest-libraries | qubership-core core, java, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 107 | qubership-core-restclient | qubership-core core, java, lib |
11 | 11 | 15 | 15 | 11 | 11 | 10 | 10 | 10 | 10 | 10 | 10 |
| 108 | qubership-core-site-management | qubership-core cloud-core, core, go |
0 | 0 | 0 | 0 | 14 | 14 | 13 | 11 | 11 | 11 | 11 | 11 |
| 109 | qubership-core-springboot-starter | qubership-core core, java, lib |
10 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 110 | qubership-core-utils | qubership-core core, java, lib |
10 | 11 | 15 | 15 | 11 | 11 | 10 | 10 | 10 | 10 | 10 | 10 |
| 111 | qubership-cql-driver | qubership-infra |
13 | 13 | 15 | 15 | 15 | 15 | 14 | 14 | 14 | 14 | 14 | 14 |
| 112 | qubership-credential-manager | qubership-infra |
10 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 113 | qubership-dbaas | qubership-core core, dbaas, java |
8 | 9 | 9 | 9 | 9 | 9 | 8 | 6 | 6 | 6 | 6 | 6 |
| 114 | qubership-dbaas-adapter-core | qubership-core |
12 | 12 | 13 | 13 | 13 | 13 | 12 | 12 | 12 | 12 | 12 | 12 |
| 115 | qubership-dbaas-client | qubership-core core, dbaas, java, lib |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 116 | qubership-deployment-status-provisioner | qubership-infra saqs |
12 | 12 | 15 | 15 | 15 | 15 | 14 | 14 | 14 | 14 | 14 | 11 |
| 117 | qubership-diag-proxy | qubership-ossf-request observability, proxy |
5 | 5 | 9 | 5 | 5 | 5 | 4 | 4 | 4 | 5 | 5 | 5 |
| 118 | qubership-disaster-recovery-daemon | qubership-infra k8sstream |
11 | 11 | 14 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 6 |
| 119 | qubership-docker-integration-tests | qubership-infra saqs |
11 | 11 | 14 | 12 | 12 | 12 | 11 | 11 | 11 | 11 | 11 | 11 |
| 120 | qubership-docker-opensearch | qubership-infra opensearch, saqs |
12 | 12 | 15 | 11 | 11 | 11 | 10 | 10 | 10 | 10 | 10 | 10 |
| 121 | qubership-env-checker | qubership-ossf-request observability |
9 | 9 | 9 | 6 | 6 | 6 | 5 | 5 | 5 | 6 | 6 | 6 |
| 122 | qubership-envgene | qubership-devops |
12 | 12 | 15 | 11 | 11 | 9 | 9 | 8 | 8 | 5 | 5 | 5 |
| 123 | qubership-envgene-instance | qubership-devops |
12 | 4 | 7 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 |
| 124 | qubership-envgene-template | qubership-devops |
13 | 5 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 |
| 125 | qubership-external-logging-installer | qubership-ossf-request logging, observability |
8 | 8 | 9 | 6 | 6 | 6 | 5 | 5 | 5 | 5 | 5 | 5 |
| 126 | qubership-fluent-pipeline-tests | qubership-ossf-request logging, observability, testing |
9 | 9 | 8 | 8 | 4 | 4 | 4 | 4 | 5 | 5 | 5 | 5 |
| 127 | qubership-fluentd | qubership-ossf-request logging, observability |
8 | 8 | 9 | 9 | 4 | 4 | 4 | 4 | 4 | 5 | 5 | 5 |
| 128 | qubership-git-system-follower | qubership-devops |
11 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 129 | qubership-grafana-plugins-init | qubership-ossf-request monitoring, observability |
9 | 9 | 8 | 8 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
| 130 | qubership-grafana-reporter | qubership-ossf-request monitoring, observability |
7 | 7 | 7 | 5 | 5 | 5 | 4 | 4 | 5 | 5 | 5 | 5 |
| 131 | qubership-graphite-remote-adapter | qubership-ossf-request monitoring, observability |
4 | 4 | 6 | 5 | 5 | 5 | 7 | 7 | 7 | 7 | 7 | 7 |
| 132 | qubership-graylog-archiving-plugin | qubership-ossf-request logging, observability, plugin |
9 | 9 | 8 | 8 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
| 133 | qubership-graylog-auth-proxy | qubership-ossf-request logging, observability, proxy |
8 | 8 | 7 | 4 | 4 | 4 | 4 | 4 | 4 | 5 | 5 | 5 |
| 134 | qubership-graylog-obfuscation-plugin | qubership-ossf-request logging, observability, plugin |
6 | 6 | 4 | 4 | 4 | 4 | 3 | 5 | 5 | 5 | 5 | 5 |
| 135 | qubership-graylog-plugins-init | qubership-ossf-request logging, observability |
0 | 5 | 7 | 4 | 4 | 4 | 5 | 5 | 5 | 5 | 5 | 5 |
| 136 | qubership-hive-metastore | qubership-infra |
10 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 137 | qubership-hub-test | qubership-devops |
0 | 0 | 0 | 15 | 15 | 15 | 15 | 15 | 14 | 14 | 14 | 14 |
| 138 | qubership-integration-catalog-library | qubership-integration broadcast-pilot, qip |
5 | 5 | 5 | 4 | 4 | 5 | 5 | 5 | 5 | 6 | 6 | 6 |
| 139 | qubership-integration-checkstyle | qubership-integration qip |
12 | 12 | 16 | 16 | 14 | 14 | 13 | 13 | 13 | 8 | 8 | 8 |
| 140 | qubership-integration-designtime-catalog | qubership-integration broadcast-pilot, qip |
6 | 6 | 9 | 5 | 5 | 6 | 6 | 6 | 6 | 7 | 7 | 7 |
| 141 | qubership-integration-engine | qubership-integration broadcast-pilot, qip |
11 | 8 | 8 | 7 | 7 | 7 | 6 | 7 | 7 | 7 | 7 | 7 |
| 142 | qubership-integration-platform | qubership-integration broadcast-pilot, qip |
5 | 5 | 8 | 8 | 4 | 4 | 5 | 5 | 5 | 6 | 5 | 5 |
| 143 | qubership-integration-runtime-catalog | qubership-integration broadcast-pilot, qip |
6 | 6 | 9 | 9 | 5 | 6 | 6 | 6 | 6 | 7 | 7 | 7 |
| 144 | qubership-integration-schemas | qubership-integration qip |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 14 | 14 | 11 | 11 | 11 |
| 145 | qubership-integration-sessions-management | qubership-integration broadcast-pilot, qip |
6 | 6 | 6 | 5 | 5 | 6 | 6 | 6 | 6 | 7 | 7 | 7 |
| 146 | qubership-integration-ui | qubership-integration qip |
12 | 12 | 15 | 15 | 15 | 15 | 14 | 14 | 11 | 9 | 9 | 9 |
| 147 | qubership-integration-variables-management | qubership-integration broadcast-pilot, qip |
7 | 7 | 7 | 6 | 6 | 7 | 7 | 7 | 7 | 8 | 7 | 7 |
| 148 | qubership-inventory-tool-cli | qubership-ossf-request observability |
11 | 6 | 7 | 6 | 6 | 6 | 5 | 5 | 5 | 6 | 6 | 6 |
| 149 | qubership-inventory-tool-core | qubership-ossf-request observability |
13 | 8 | 8 | 8 | 8 | 8 | 7 | 7 | 7 | 8 | 8 | 8 |
| 150 | qubership-jaeger | qubership-ossf-request broadcast-pilot, observability, tracing |
8 | 8 | 8 | 7 | 5 | 5 | 4 | 4 | 4 | 5 | 5 | 5 |
| 151 | qubership-kafka | qubership-infra kafka, saqs |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 | 13 | 13 |
| 152 | qubership-kube-events-generator | qubership-ossf-request logging, observability, testing |
4 | 4 | 7 | 5 | 4 | 4 | 5 | 5 | 5 | 5 | 5 | 5 |
| 153 | qubership-kube-events-reader | qubership-ossf-request logging, observability |
7 | 7 | 8 | 8 | 4 | 4 | 4 | 4 | 4 | 5 | 5 | 5 |
| 154 | qubership-landscape-config | qubership-landscape |
8 | 8 | 9 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 |
| 155 | qubership-landscape-config-processor | qubership-landscape |
8 | 8 | 9 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 |
| 156 | qubership-log-exporter | qubership-ossf-request logging, observability |
7 | 7 | 8 | 8 | 5 | 5 | 4 | 4 | 5 | 5 | 5 | 5 |
| 157 | qubership-log-generator | qubership-ossf-request logging, observability |
7 | 7 | 5 | 6 | 5 | 5 | 5 | 5 | 5 | 6 | 6 | 6 |
| 158 | qubership-logging-operator | qubership-ossf-request logging, observability |
7 | 7 | 7 | 8 | 8 | 8 | 7 | 7 | 7 | 8 | 8 | 8 |
| 159 | qubership-maas | qubership-core core, go, maas |
8 | 8 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 160 | qubership-maas-client | qubership-core core, java, lib, maas |
8 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 161 | qubership-maas-client-quarkus | qubership-core core, java, lib, maas |
9 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 162 | qubership-maas-client-spring | qubership-core core, java, lib, maas |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 163 | qubership-maas-declarative-client-commons | qubership-core core, java, lib, maas |
9 | 9 | 9 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 164 | qubership-maas-declarative-client-quarkus | qubership-core core, java, lib, maas |
9 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 165 | qubership-maas-declarative-client-spring | qubership-core core, java, lib, maas |
8 | 9 | 9 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 166 | qubership-mistral | qubership-infra |
13 | 13 | 14 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 167 | qubership-mistral-operator | qubership-infra |
0 | 0 | 14 | 14 | 11 | 11 | 9 | 9 | 9 | 9 | 9 | 9 |
| 168 | qubership-mongodb-driver | qubership-infra |
12 | 12 | 13 | 13 | 13 | 13 | 12 | 12 | 12 | 12 | 12 | 12 |
| 169 | qubership-monitoring-operator | qubership-ossf-request monitoring, observability |
8 | 8 | 8 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 7 | 7 |
| 170 | qubership-network-latency-exporter | qubership-ossf-request monitoring, observability |
4 | 4 | 8 | 8 | 5 | 5 | 4 | 4 | 5 | 5 | 5 | 5 |
| 171 | qubership-nifi | qubership-nifi nifi |
2 | 2 | 3 | 3 | 4 | 3 | 5 | 5 | 5 | 5 | 5 | 5 |
| 172 | qubership-nifi-registry | qubership-nifi nifi-registry |
1 | 2 | 6 | 3 | 3 | 3 | 5 | 5 | 5 | 5 | 5 | 5 |
| 173 | qubership-nosqldb-operator-core | qubership-infra |
13 | 13 | 15 | 12 | 12 | 12 | 11 | 11 | 11 | 11 | 11 | 11 |
| 174 | qubership-observability-examples | qubership-observability examples, observability |
8 | 8 | 9 | 7 | 7 | 7 | 7 | 7 | 8 | 8 | 8 | 8 |
| 175 | qubership-observability-operator | qubership-observability observability |
11 | 4 | 9 | 9 | 4 | 4 | 6 | 6 | 6 | 6 | 6 | 6 |
| 176 | qubership-open-telemetry-collector | qubership-ossf-request observability |
9 | 9 | 9 | 8 | 4 | 4 | 3 | 3 | 5 | 5 | 5 | 5 |
| 177 | qubership-opensearch | qubership-infra opensearch, saqs |
11 | 11 | 14 | 14 | 14 | 14 | 13 | 13 | 13 | 13 | 13 | 10 |
| 178 | qubership-opensearch-curator | qubership-infra opensearch, saqs |
11 | 11 | 11 | 10 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 179 | qubership-opensearch-dbaas-adapter | qubership-infra opensearch, saqs |
11 | 11 | 14 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 180 | qubership-opensearch-monitoring | qubership-infra opensearch, saqs |
11 | 11 | 14 | 14 | 10 | 9 | 9 | 9 | 9 | 9 | 9 | 9 |
| 181 | qubership-opentelemetry-helm-charts | qubership-observability observability |
9 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 8 | 8 |
| 182 | qubership-pipelines-cli-command-samples | qubership-devops |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 9 | 9 | 9 | 9 |
| 183 | qubership-pipelines-common-python-library | qubership-devops |
8 | 8 | 5 | 5 | 2 | 2 | 2 | 2 | 2 | 5 | 5 | 5 |
| 184 | qubership-pipelines-declarative-executor | qubership-devops |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 | 6 | 9 | 9 | 9 |
| 185 | qubership-pipelines-modules-ops | qubership-devops |
0 | 0 | 15 | 11 | 10 | 9 | 2 | 5 | 5 | 5 | 5 | 5 |
| 186 | qubership-profiler-agent | qubership-ossf-request broadcast-pilot, observability, profiler |
7 | 7 | 8 | 12 | 12 | 11 | 10 | 10 | 10 | 10 | 10 | 9 |
| 187 | qubership-prometheus-adapter-operator | qubership-ossf-request monitoring, observability |
9 | 9 | 9 | 9 | 9 | 9 | 8 | 8 | 9 | 9 | 9 | 9 |
| 188 | qubership-query-exporter | qubership-infra |
12 | 12 | 15 | 15 | 11 | 11 | 10 | 10 | 10 | 7 | 7 | 7 |
| 189 | qubership-renovate-config | qubership-devops |
13 | 13 | 14 | 14 | 14 | 14 | 14 | 14 | 14 | 14 | 14 | 14 |
| 190 | qubership-repo-template | qubership-devops |
10 | 9 | 9 | 9 | 10 | 9 | 9 | 9 | 5 | 5 | 5 | 5 |
| 191 | qubership-spark-on-k8s | qubership-infra |
0 | 0 | 0 | 0 | 0 | 15 | 15 | 14 | 14 | 14 | 14 | 14 |
| 192 | qubership-tcp-duplicator | qubership-ossf-request logging, observability |
9 | 9 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 5 | 5 | 5 |
| 193 | qubership-test-pipelines | qubership-devops |
13 | 13 | 14 | 14 | 10 | 9 | 10 | 10 | 10 | 10 | 10 | 10 |
| 194 | qubership-testing-platform-adapter-robot-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 | 8 | 8 | 8 |
| 195 | qubership-testing-platform-auth-library | qubership-tp |
0 | 0 | 0 | 0 | 12 | 12 | 8 | 5 | 5 | 7 | 7 | 7 |
| 196 | qubership-testing-platform-common-auditing-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 | 7 | 8 | 8 | 8 |
| 197 | qubership-testing-platform-common-library | qubership-tp |
0 | 0 | 0 | 0 | 12 | 12 | 8 | 5 | 7 | 7 | 7 | 7 |
| 198 | qubership-testing-platform-configuration-dataset-excel-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 | 6 | 7 | 7 | 7 |
| 199 | qubership-testing-platform-crypt-library | qubership-tp |
0 | 0 | 0 | 0 | 12 | 12 | 8 | 5 | 5 | 7 | 7 | 7 |
| 200 | qubership-testing-platform-datasets | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 | 9 | 9 | 9 |
| 201 | qubership-testing-platform-diameter-transport-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 | 7 | 7 | 7 | 7 |
| 202 | qubership-testing-platform-environments | qubership-tp |
0 | 0 | 0 | 0 | 0 | 12 | 5 | 6 | 6 | 9 | 9 | 9 |
| 203 | qubership-testing-platform-export-import-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 12 | 9 | 6 | 6 | 7 | 7 | 7 |
| 204 | qubership-testing-platform-integration-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 11 | 8 | 5 | 5 | 7 | 7 | 7 |
| 205 | qubership-testing-platform-itf-core-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 | 5 | 8 | 8 | 8 |
| 206 | qubership-testing-platform-itf-executor | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 | 5 | 8 | 8 | 8 |
| 207 | qubership-testing-platform-itf-lite-backend | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 | 8 | 8 | 8 |
| 208 | qubership-testing-platform-itf-reporting | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 11 | 11 | 8 | 8 | 8 |
| 209 | qubership-testing-platform-itf-stubs | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 11 | 5 | 8 | 8 | 8 |
| 210 | qubership-testing-platform-macros-core-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 | 8 | 8 | 8 |
| 211 | qubership-testing-platform-multitenancy-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 | 6 | 8 | 8 | 8 |
| 212 | qubership-testing-platform-ram | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 | 8 | 8 | 8 |
| 213 | qubership-testing-platform-ss7-transport-library | qubership-tp |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 | 7 | 7 | 7 | 7 |
| 214 | qubership-trino | qubership-infra |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 | 13 | 13 |
| 215 | qubership-version-exporter | qubership-ossf-request monitoring, observability |
4 | 4 | 7 | 7 | 3 | 3 | 5 | 5 | 5 | 5 | 5 | 5 |
| 216 | qubership-workflow-hub | qubership-devops |
8 | 8 | 8 | 9 | 9 | 9 | 8 | 8 | 8 | 8 | 7 | 7 |
| 217 | qubership-zookeeper | qubership-infra saqs, zookeeper |
11 | 9 | 14 | 14 | 14 | 14 | 13 | 13 | 13 | 13 | 13 | 13 |
| 218 | release-drafter | qubership-devops |
0 | 0 | 0 | 0 | 0 | 0 | 15 | 15 | 14 | 14 | 14 | 14 |
| 219 | robot-shop | qubership-observability example, observability |
9 | 9 | 9 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
| # | ID | Team | Code Coverage Status❔ | Java Version | Open Pull Requests Count | Updated At |
|---|---|---|---|---|---|---|
| 1 | .github | qubership-devops |
Not registered ❌ | ❌ | 2025-06-27 | |
| 2 | KubeMarine | qubership-infra administration, devops, helm, k8sstream, kubernetes |
Not registered ❌ | ❌ | 2025-06-26 | |
| 3 | base-images-module-base | qubership-infra base-image |
Not registered ❌ | ❌ | 2025-06-25 | |
| 4 | cassandra | ❌ | Not registered ❌ | ❌ | 2025-06-10 | |
| 5 | cassandra-exporter | qubership-infra |
Not registered ❌ | 1.8 | ❌ | 2025-04-16 |
| 6 | chart-releaser-action | qubership-devops |
Not registered ❌ | ❌ | 2025-05-28 | |
| 7 | cla-storage | qubership-infra |
Not registered ❌ | ❌ | 2025-06-27 | |
| 8 | gatekeeper-library | qubership-infra |
Not registered ❌ | ❌ | 2025-04-16 | |
| 9 | get-package-ids | qubership-infra |
Not registered ❌ | ❌ | 2025-04-16 | |
| 10 | k8s-conformance | qubership-infra |
Not registered ❌ | ❌ | 2025-04-16 | |
| 11 | kafka | ❌ | Not registered ❌ | Not specified ❌ | ❌ | 2025-06-10 |
| 12 | keycloak | ❌ | Not registered ❌ | 8 | ❌ | 2025-06-17 |
| 13 | microservice-restclient | qubership-infra |
93.0% | ❌ | 2025-04-16 | |
| 14 | pg_hint_plan | qubership-infra |
Not registered ❌ | ❌ | 2025-04-16 | |
| 15 | pgskipper-backup-daemon | qubership-infra |
Not registered ❌ | ❌ | 2025-06-23 | |
| 16 | pgskipper-dbaas-adapter | qubership-infra |
Not registered ❌ | ❌ | 2025-05-14 | |
| 17 | pgskipper-monitoring-agent | qubership-infra |
Not registered ❌ | ❌ | 2025-06-12 | |
| 18 | pgskipper-operator | qubership-infra |
Not registered ❌ | ❌ | 2025-06-25 | |
| 19 | pgskipper-operator-core | qubership-infra |
Not registered ❌ | ❌ | 2025-05-02 | |
| 20 | pgskipper-patroni | qubership-infra |
Not registered ❌ | ❌ | 2025-06-23 | |
| 21 | pgskipper-pgbackrest-sidecar | qubership-infra |
Not registered ❌ | ❌ | 2025-06-27 | |
| 22 | pgskipper-replication-controller | qubership-infra |
Not registered ❌ | ❌ | 2025-04-16 | |
| 23 | pgskipper-upgrade | qubership-infra |
Not registered ❌ | ❌ | 2025-06-23 | |
| 24 | postgres | ❌ | Not registered ❌ | ❌ | 2025-06-18 | |
| 25 | qubership-airflow | qubership-infra |
Not registered ❌ | ❌ | 2025-06-26 | |
| 26 | qubership-api-linter-service | qubership-apihub apihub |
Not registered ❌ | ❌ | 2025-06-23 | |
| 27 | qubership-apihub | qubership-apihub apihub |
Not registered ❌ | ❌ | 2025-06-25 | |
| 28 | qubership-apihub-agent | qubership-apihub apihub |
Not registered ❌ | ❌ | 2025-06-24 | |
| 29 | qubership-apihub-api-data-model | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-06 | |
| 30 | qubership-apihub-api-diff | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-10 | |
| 31 | qubership-apihub-api-doc-viewer | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-10 | |
| 32 | qubership-apihub-api-processor | qubership-apihub apihub, broadcast-pilot, frontend |
Not registered ❌ | ❌ | 2025-06-20 | |
| 33 | qubership-apihub-api-unifier | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-25 | |
| 34 | qubership-apihub-api-visitor | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-23 | |
| 35 | qubership-apihub-apispec-view | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-25 | |
| 36 | qubership-apihub-backend | qubership-apihub apihub, broadcast-pilot |
Not registered ❌ | ❌ | 2025-06-26 | |
| 37 | qubership-apihub-build-task-consumer | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-20 | |
| 38 | qubership-apihub-ci | qubership-apihub apihub |
Not registered ❌ | ❌ | 2025-06-04 | |
| 39 | qubership-apihub-class-view | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-05-21 | |
| 40 | qubership-apihub-compatibility-suites | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-05-21 | |
| 41 | qubership-apihub-graphapi | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-05-21 | |
| 42 | qubership-apihub-http-spec | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-06 | |
| 43 | qubership-apihub-jest-chrome-in-docker-environment | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-05-21 | |
| 44 | qubership-apihub-json-crawl | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-05-21 | |
| 45 | qubership-apihub-nodejs-dev-image | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-04 | |
| 46 | qubership-apihub-npm-gitflow | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-05-21 | |
| 47 | qubership-apihub-postman-collections | qubership-apihub apihub |
Not registered ❌ | ❌ | 2025-06-19 | |
| 48 | qubership-apihub-protobufjs-research | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-04-02 | |
| 49 | qubership-apihub-rest-playground | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-25 | |
| 50 | qubership-apihub-sniffer-agent | qubership-apihub apihub |
Not registered ❌ | ❌ | 2025-06-13 | |
| 51 | qubership-apihub-test-service | qubership-apihub apihub |
Not registered ❌ | ❌ | 2025-06-13 | |
| 52 | qubership-apihub-traffic-analyzer | qubership-apihub apihub |
Not registered ❌ | ❌ | 2025-06-24 | |
| 53 | qubership-apihub-ui | qubership-apihub apihub, broadcast-pilot, frontend |
Not registered ❌ | ❌ | 2025-06-25 | |
| 54 | qubership-apihub-ui-tests | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-25 | |
| 55 | qubership-apihub-vscode | qubership-apihub apihub, frontend |
Not registered ❌ | ❌ | 2025-06-26 | |
| 56 | qubership-av-scan-service | qubership-infra |
Not registered ❌ | ❌ | 2025-06-13 | |
| 57 | qubership-backup-daemon | qubership-infra saqs |
Not registered ❌ | ❌ | 2025-05-23 | |
| 58 | qubership-cloud-passport-cli | qubership-devops |
Not registered ❌ | ❌ | 2025-05-06 | |
| 59 | qubership-colly | qubership-devops broadcast-pilot |
84.9% | 21 | ❌ | 2025-06-27 |
| 60 | qubership-consul | qubership-devops consul, saqs |
Not registered ❌ | ❌ | 2025-06-16 | |
| 61 | qubership-consul-acl-configurator | qubership-devops consul, saqs |
Not registered ❌ | ❌ | 2025-06-02 | |
| 62 | qubership-consul-backup-daemon | qubership-devops consul, saqs |
Not registered ❌ | ❌ | 2025-06-02 | |
| 63 | qubership-core-base-images | qubership-core base-image, core |
Not registered ❌ | ❌ | 2025-06-13 | |
| 64 | qubership-core-blue-green-state-monitor | qubership-core core, java, lib |
81.5% | 17 | ❌ | 2025-06-17 |
| 65 | qubership-core-blue-green-state-monitor-quarkus | qubership-core core, java, lib |
89.1% | 17 | ❌ | 2025-06-17 |
| 66 | qubership-core-bootstrap | qubership-core core |
Not registered ❌ | ❌ | 2025-06-20 | |
| 67 | qubership-core-config-server | qubership-core cloud-core, core, java, spring |
80.8% | ${java.version} | ❌ | 2025-06-04 |
| 68 | qubership-core-context-propagation | qubership-core core, java, lib |
77.5% | 17 | ❌ | 2025-06-25 |
| 69 | qubership-core-context-propagation-quarkus | qubership-core core, java, lib |
94.7% | 17 | ❌ | 2025-06-16 |
| 70 | qubership-core-control-plane | qubership-core cloud-core, core, go, service-mesh |
57.9% | 11 | ❌ | 2025-05-27 |
| 71 | qubership-core-core-operator | qubership-core cloud-core, core, java, quarkus |
74.5% | 21 | ❌ | 2025-06-04 |
| 72 | qubership-core-dbaas-agent | qubership-core cloud-core, core, go |
70.5% | ❌ | 2025-05-28 | |
| 73 | qubership-core-error-handling | qubership-core core, java, lib |
96.4% | 17 | ❌ | 2025-06-17 |
| 74 | qubership-core-facade-operator | qubership-core cloud-core, core, go |
64.1% | ❌ | 2025-05-28 | |
| 75 | qubership-core-infra | qubership-core core |
0.0% | Not specified ❌ | ❌ | 2025-06-17 |
| 76 | qubership-core-ingress-gateway | qubership-core cloud-core, core, envoy, service-mesh |
Not registered ❌ | ❌ | 2025-05-22 | |
| 77 | qubership-core-junit-k8s-extension | qubership-core core, java, lib |
63.0% | ${java.version} | ❌ | 2025-06-04 |
| 78 | qubership-core-lib-go | qubership-core core, go, lib |
79.4% | ❌ | 2025-05-27 | |
| 79 | qubership-core-lib-go-actuator-common | qubership-core core, go, lib |
81.5% | ❌ | 2025-05-27 | |
| 80 | qubership-core-lib-go-bg-kafka | qubership-core core, go, lib |
43.5% | ❌ | 2025-05-27 | |
| 81 | qubership-core-lib-go-bg-state-monitor | qubership-core core, go, lib |
87.0% | ❌ | 2025-06-16 | |
| 82 | qubership-core-lib-go-dbaas-arangodb-client | qubership-core core, go, lib |
82.5% | ❌ | 2025-05-27 | |
| 83 | qubership-core-lib-go-dbaas-base-client | qubership-core core, go, lib |
82.1% | ❌ | 2025-05-27 | |
| 84 | qubership-core-lib-go-dbaas-cassandra-client | qubership-core core, go, lib |
81.7% | ❌ | 2025-05-27 | |
| 85 | qubership-core-lib-go-dbaas-clickhouse-client | qubership-core core, go, lib |
82.7% | ❌ | 2025-05-27 | |
| 86 | qubership-core-lib-go-dbaas-mongo-client | qubership-core core, go, lib |
86.7% | ❌ | 2025-06-14 | |
| 87 | qubership-core-lib-go-dbaas-opensearch-client | qubership-core core, go, lib |
76.3% | ❌ | 2025-05-27 | |
| 88 | qubership-core-lib-go-dbaas-postgres-client | qubership-core core, go, lib |
86.4% | ❌ | 2025-05-27 | |
| 89 | qubership-core-lib-go-error-handling | qubership-core core, go, lib |
71.2% | ❌ | 2025-05-27 | |
| 90 | qubership-core-lib-go-fiber-server-utils | qubership-core core, go, lib |
76.2% | ❌ | 2025-05-27 | |
| 91 | qubership-core-lib-go-maas-bg-segmentio | qubership-core core, go, lib |
85.7% | ❌ | 2025-05-27 | |
| 92 | qubership-core-lib-go-maas-client | qubership-core core, go, lib |
46.2% | ❌ | 2025-06-25 | |
| 93 | qubership-core-lib-go-maas-core | qubership-core core, go, lib |
54.7% | ❌ | 2025-05-27 | |
| 94 | qubership-core-lib-go-maas-segmentio | qubership-core core, go, lib |
75.7% | ❌ | 2025-06-25 | |
| 95 | qubership-core-lib-go-paas-mediation-client | qubership-core core, go, lib |
78.4% | ❌ | 2025-06-20 | |
| 96 | qubership-core-lib-go-rest-utils | qubership-core core, go, lib |
85.1% | ❌ | 2025-05-27 | |
| 97 | qubership-core-lib-go-stomp-websocket | qubership-core core, go, lib |
18.5% | ❌ | 2025-05-27 | |
| 98 | qubership-core-maas-agent | qubership-core cloud-core, core, go |
57.3% | ❌ | 2025-05-28 | |
| 99 | qubership-core-microservice-dependencies | qubership-core core, java, lib |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-17 |
| 100 | qubership-core-microservice-framework | qubership-core core, java, lib |
89.4% | Not specified ❌ | ❌ | 2025-06-17 |
| 101 | qubership-core-microservice-framework-extensions | qubership-core core, java, lib |
87.0% | Not specified ❌ | ❌ | 2025-06-16 |
| 102 | qubership-core-mongo-evolution | qubership-core core, java, lib |
84.8% | 17 | ❌ | 2025-06-16 |
| 103 | qubership-core-paas-mediation | qubership-core cloud-core, core, go |
80.6% | ❌ | 2025-05-28 | |
| 104 | qubership-core-process-orchestrator | qubership-core core, java, lib |
85.2% | 21 | ❌ | 2025-06-16 |
| 105 | qubership-core-quarkus-extensions | qubership-core core, java, lib |
72.1% | 17 | ❌ | 2025-06-17 |
| 106 | qubership-core-rest-libraries | qubership-core core, java, lib |
76.6% | 17 | ❌ | 2025-06-17 |
| 107 | qubership-core-restclient | qubership-core core, java, lib |
93.0% | Not specified ❌ | ❌ | 2025-06-17 |
| 108 | qubership-core-site-management | qubership-core cloud-core, core, go |
26.2% | ❌ | 2025-05-28 | |
| 109 | qubership-core-springboot-starter | qubership-core core, java, lib |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-17 |
| 110 | qubership-core-utils | qubership-core core, java, lib |
78.3% | Not specified ❌ | ❌ | 2025-06-16 |
| 111 | qubership-cql-driver | qubership-infra |
Not registered ❌ | ❌ | 2025-04-16 | |
| 112 | qubership-credential-manager | qubership-infra |
Not registered ❌ | ❌ | 2025-06-09 | |
| 113 | qubership-dbaas | qubership-core core, dbaas, java |
63.5% | 21 | ❌ | 2025-06-25 |
| 114 | qubership-dbaas-adapter-core | qubership-core |
Not registered ❌ | ❌ | 2025-04-16 | |
| 115 | qubership-dbaas-client | qubership-core core, dbaas, java, lib |
82.1% | 8 | ❌ | 2025-06-17 |
| 116 | qubership-deployment-status-provisioner | qubership-infra saqs |
Not registered ❌ | ❌ | 2025-06-24 | |
| 117 | qubership-diag-proxy | qubership-ossf-request observability, proxy |
Not registered ❌ | ❌ | 2025-06-19 | |
| 118 | qubership-disaster-recovery-daemon | qubership-infra k8sstream |
Not registered ❌ | ❌ | 2025-06-18 | |
| 119 | qubership-docker-integration-tests | qubership-infra saqs |
Not registered ❌ | ❌ | 2025-06-09 | |
| 120 | qubership-docker-opensearch | qubership-infra opensearch, saqs |
Not registered ❌ | 11 | ❌ | 2025-06-19 |
| 121 | qubership-env-checker | qubership-ossf-request observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 122 | qubership-envgene | qubership-devops |
Not registered ❌ | 11 | ❌ | 2025-06-27 |
| 123 | qubership-envgene-instance | qubership-devops |
Not registered ❌ | ❌ | 2025-04-16 | |
| 124 | qubership-envgene-template | qubership-devops |
Not registered ❌ | Not specified ❌ | ❌ | 2025-05-20 |
| 125 | qubership-external-logging-installer | qubership-ossf-request logging, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 126 | qubership-fluent-pipeline-tests | qubership-ossf-request logging, observability, testing |
Not registered ❌ | ❌ | 2025-06-19 | |
| 127 | qubership-fluentd | qubership-ossf-request logging, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 128 | qubership-git-system-follower | qubership-devops |
Not registered ❌ | ❌ | 2025-06-23 | |
| 129 | qubership-grafana-plugins-init | qubership-ossf-request monitoring, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 130 | qubership-grafana-reporter | qubership-ossf-request monitoring, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 131 | qubership-graphite-remote-adapter | qubership-ossf-request monitoring, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 132 | qubership-graylog-archiving-plugin | qubership-ossf-request logging, observability, plugin |
Not registered ❌ | 1.8 | ❌ | 2025-06-19 |
| 133 | qubership-graylog-auth-proxy | qubership-ossf-request logging, observability, proxy |
Not registered ❌ | ❌ | 2025-06-19 | |
| 134 | qubership-graylog-obfuscation-plugin | qubership-ossf-request logging, observability, plugin |
Not registered ❌ | 1.8 | ❌ | 2025-06-25 |
| 135 | qubership-graylog-plugins-init | qubership-ossf-request logging, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 136 | qubership-hive-metastore | qubership-infra |
Not registered ❌ | ❌ | 2025-04-16 | |
| 137 | qubership-hub-test | qubership-devops |
Not registered ❌ | ❌ | 2025-05-28 | |
| 138 | qubership-integration-catalog-library | qubership-integration broadcast-pilot, qip |
Not registered ❌ | 21 | ❌ | 2025-06-17 |
| 139 | qubership-integration-checkstyle | qubership-integration qip |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-11 |
| 140 | qubership-integration-designtime-catalog | qubership-integration broadcast-pilot, qip |
0.0% | Not specified ❌ | ❌ | 2025-06-26 |
| 141 | qubership-integration-engine | qubership-integration broadcast-pilot, qip |
0.0% | Not specified ❌ | ❌ | 2025-06-26 |
| 142 | qubership-integration-platform | qubership-integration broadcast-pilot, qip |
Not registered ❌ | ❌ | 2025-06-21 | |
| 143 | qubership-integration-runtime-catalog | qubership-integration broadcast-pilot, qip |
0.0% | Not specified ❌ | ❌ | 2025-06-26 |
| 144 | qubership-integration-schemas | qubership-integration qip |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-20 |
| 145 | qubership-integration-sessions-management | qubership-integration broadcast-pilot, qip |
0.0% | Not specified ❌ | ❌ | 2025-06-26 |
| 146 | qubership-integration-ui | qubership-integration qip |
Not registered ❌ | ❌ | 2025-06-26 | |
| 147 | qubership-integration-variables-management | qubership-integration broadcast-pilot, qip |
0.0% | Not specified ❌ | ❌ | 2025-06-26 |
| 148 | qubership-inventory-tool-cli | qubership-ossf-request observability |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-27 |
| 149 | qubership-inventory-tool-core | qubership-ossf-request observability |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-27 |
| 150 | qubership-jaeger | qubership-ossf-request broadcast-pilot, observability, tracing |
Not registered ❌ | ❌ | 2025-06-23 | |
| 151 | qubership-kafka | qubership-infra kafka, saqs |
Not registered ❌ | 11 | ❌ | 2025-06-26 |
| 152 | qubership-kube-events-generator | qubership-ossf-request logging, observability, testing |
Not registered ❌ | ❌ | 2025-06-27 | |
| 153 | qubership-kube-events-reader | qubership-ossf-request logging, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 154 | qubership-landscape-config | qubership-landscape |
Not registered ❌ | ❌ | 2025-06-20 | |
| 155 | qubership-landscape-config-processor | qubership-landscape |
Not registered ❌ | 11 | ❌ | 2025-06-16 |
| 156 | qubership-log-exporter | qubership-ossf-request logging, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 157 | qubership-log-generator | qubership-ossf-request logging, observability |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-19 |
| 158 | qubership-logging-operator | qubership-ossf-request logging, observability |
Not registered ❌ | ❌ | 2025-06-27 | |
| 159 | qubership-maas | qubership-core core, go, maas |
61.2% | ❌ | 2025-06-25 | |
| 160 | qubership-maas-client | qubership-core core, java, lib, maas |
87.8% | 17 | ❌ | 2025-06-17 |
| 161 | qubership-maas-client-quarkus | qubership-core core, java, lib, maas |
95.2% | 17 | ❌ | 2025-06-17 |
| 162 | qubership-maas-client-spring | qubership-core core, java, lib, maas |
100.0% | 17 | ❌ | 2025-06-17 |
| 163 | qubership-maas-declarative-client-commons | qubership-core core, java, lib, maas |
76.0% | 17 | ❌ | 2025-06-17 |
| 164 | qubership-maas-declarative-client-quarkus | qubership-core core, java, lib, maas |
74.9% | 17 | ❌ | 2025-06-17 |
| 165 | qubership-maas-declarative-client-spring | qubership-core core, java, lib, maas |
81.9% | 17 | ❌ | 2025-06-17 |
| 166 | qubership-mistral | qubership-infra |
Not registered ❌ | ❌ | 2025-06-17 | |
| 167 | qubership-mistral-operator | qubership-infra |
Not registered ❌ | ❌ | 2025-06-17 | |
| 168 | qubership-mongodb-driver | qubership-infra |
Not registered ❌ | ❌ | 2025-04-16 | |
| 169 | qubership-monitoring-operator | qubership-ossf-request monitoring, observability |
Not registered ❌ | ❌ | 2025-06-27 | |
| 170 | qubership-network-latency-exporter | qubership-ossf-request monitoring, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 171 | qubership-nifi | qubership-nifi nifi |
68.4% | 15 | ❌ | 2025-06-25 |
| 172 | qubership-nifi-registry | qubership-nifi nifi-registry |
79.8% | 17 | ❌ | 2025-06-27 |
| 173 | qubership-nosqldb-operator-core | qubership-infra |
Not registered ❌ | ❌ | 2025-04-16 | |
| 174 | qubership-observability-examples | qubership-observability examples, observability |
Not registered ❌ | ❌ | 2025-06-11 | |
| 175 | qubership-observability-operator | qubership-observability observability |
Not registered ❌ | ❌ | 2025-06-26 | |
| 176 | qubership-open-telemetry-collector | qubership-ossf-request observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 177 | qubership-opensearch | qubership-infra opensearch, saqs |
Not registered ❌ | 11 | ❌ | 2025-06-25 |
| 178 | qubership-opensearch-curator | qubership-infra opensearch, saqs |
Not registered ❌ | ❌ | 2025-06-03 | |
| 179 | qubership-opensearch-dbaas-adapter | qubership-infra opensearch, saqs |
Not registered ❌ | ❌ | 2025-06-04 | |
| 180 | qubership-opensearch-monitoring | qubership-infra opensearch, saqs |
Not registered ❌ | ❌ | 2025-06-03 | |
| 181 | qubership-opentelemetry-helm-charts | qubership-observability observability |
Not registered ❌ | ❌ | 2025-04-15 | |
| 182 | qubership-pipelines-cli-command-samples | qubership-devops |
Not registered ❌ | ❌ | 2025-06-26 | |
| 183 | qubership-pipelines-common-python-library | qubership-devops |
Not registered ❌ | ❌ | 2025-06-26 | |
| 184 | qubership-pipelines-declarative-executor | qubership-devops |
Not registered ❌ | ❌ | 2025-06-11 | |
| 185 | qubership-pipelines-modules-ops | qubership-devops |
Not registered ❌ | ❌ | 2025-06-11 | |
| 186 | qubership-profiler-agent | qubership-ossf-request broadcast-pilot, observability, profiler |
Not registered ❌ | ❌ | 2025-06-26 | |
| 187 | qubership-prometheus-adapter-operator | qubership-ossf-request monitoring, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 188 | qubership-query-exporter | qubership-infra |
Not registered ❌ | ❌ | 2025-06-11 | |
| 189 | qubership-renovate-config | qubership-devops |
Not registered ❌ | ❌ | 2025-04-16 | |
| 190 | qubership-repo-template | qubership-devops |
Not registered ❌ | ❌ | 2025-06-17 | |
| 191 | qubership-spark-on-k8s | qubership-infra |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-13 |
| 192 | qubership-tcp-duplicator | qubership-ossf-request logging, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 193 | qubership-test-pipelines | qubership-devops |
Not registered ❌ | ❌ | 2025-06-05 | |
| 194 | qubership-testing-platform-adapter-robot-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-16 |
| 195 | qubership-testing-platform-auth-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-09 |
| 196 | qubership-testing-platform-common-auditing-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-10 |
| 197 | qubership-testing-platform-common-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-09 |
| 198 | qubership-testing-platform-configuration-dataset-excel-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-10 |
| 199 | qubership-testing-platform-crypt-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-09 |
| 200 | qubership-testing-platform-datasets | qubership-tp |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-27 |
| 201 | qubership-testing-platform-diameter-transport-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-09 |
| 202 | qubership-testing-platform-environments | qubership-tp |
Not registered ❌ | Not specified ❌ | ❌ | 2025-06-25 |
| 203 | qubership-testing-platform-export-import-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-10 |
| 204 | qubership-testing-platform-integration-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-10 |
| 205 | qubership-testing-platform-itf-core-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-25 |
| 206 | qubership-testing-platform-itf-executor | qubership-tp |
Not registered ❌ | ❌ | 2025-06-25 | |
| 207 | qubership-testing-platform-itf-lite-backend | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-27 |
| 208 | qubership-testing-platform-itf-reporting | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-24 |
| 209 | qubership-testing-platform-itf-stubs | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-26 |
| 210 | qubership-testing-platform-macros-core-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-09 |
| 211 | qubership-testing-platform-multitenancy-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-10 |
| 212 | qubership-testing-platform-ram | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-27 |
| 213 | qubership-testing-platform-ss7-transport-library | qubership-tp |
Not registered ❌ | 1.8 | ❌ | 2025-06-09 |
| 214 | qubership-trino | qubership-infra |
Not registered ❌ | ❌ | 2025-06-11 | |
| 215 | qubership-version-exporter | qubership-ossf-request monitoring, observability |
Not registered ❌ | ❌ | 2025-06-19 | |
| 216 | qubership-workflow-hub | qubership-devops |
Not registered ❌ | ❌ | 2025-06-26 | |
| 217 | qubership-zookeeper | qubership-infra saqs, zookeeper |
Not registered ❌ | ❌ | 2025-06-27 | |
| 218 | release-drafter | qubership-devops |
Not registered ❌ | ❌ | 2025-05-28 | |
| 219 | robot-shop | qubership-observability example, observability |
Not registered ❌ | Not specified ❌ | ❌ | 2025-04-18 |
| # | ID | Team | /License❔ | /README | AddCommitMsg❔ | CLA❔ | Code Owners❔ | ConvCommits❔ | Do not use Prettier | Labeler❔ | Lint-Title❔ | ProfanityFilter❔ | SuperLinter❔ |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | .github | qubership-devops |
❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ✅ |
| 2 | KubeMarine | qubership-infra administration, devops, helm, k8sstream, kubernetes |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 3 | base-images-module-base | qubership-infra base-image |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 4 | cassandra | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 5 | cassandra-exporter | qubership-infra |
❌ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 6 | chart-releaser-action | qubership-devops |
⛅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 7 | cla-storage | qubership-infra |
❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 8 | gatekeeper-library | qubership-infra |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 9 | get-package-ids | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 10 | k8s-conformance | qubership-infra |
⛅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 11 | kafka | ❌ | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 12 | keycloak | ❌ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 13 | microservice-restclient | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 14 | pg_hint_plan | qubership-infra |
❌ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 15 | pgskipper-backup-daemon | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 16 | pgskipper-dbaas-adapter | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 17 | pgskipper-monitoring-agent | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 18 | pgskipper-operator | qubership-infra |
✅ | ✅ | ❌ | 😱 | ❌ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ |
| 19 | pgskipper-operator-core | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 20 | pgskipper-patroni | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 21 | pgskipper-pgbackrest-sidecar | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 22 | pgskipper-replication-controller | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 23 | pgskipper-upgrade | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 24 | postgres | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 25 | qubership-airflow | qubership-infra |
✅ | ✅ | ❌ | 😱 | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 26 | qubership-api-linter-service | qubership-apihub apihub |
✅ | ✅ | ✅ | 😱 | ✅ | 😱 | ❌ | ✅ | 😱 | ✅ | ❌ |
| 27 | qubership-apihub | qubership-apihub apihub |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 28 | qubership-apihub-agent | qubership-apihub apihub |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 29 | qubership-apihub-api-data-model | qubership-apihub apihub, frontend |
✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 30 | qubership-apihub-api-diff | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 31 | qubership-apihub-api-doc-viewer | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 32 | qubership-apihub-api-processor | qubership-apihub apihub, broadcast-pilot, frontend |
✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 33 | qubership-apihub-api-unifier | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 34 | qubership-apihub-api-visitor | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 35 | qubership-apihub-apispec-view | qubership-apihub apihub, frontend |
✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 36 | qubership-apihub-backend | qubership-apihub apihub, broadcast-pilot |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 37 | qubership-apihub-build-task-consumer | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 38 | qubership-apihub-ci | qubership-apihub apihub |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 39 | qubership-apihub-class-view | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 40 | qubership-apihub-compatibility-suites | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 41 | qubership-apihub-graphapi | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 42 | qubership-apihub-http-spec | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 43 | qubership-apihub-jest-chrome-in-docker-environment | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 44 | qubership-apihub-json-crawl | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 45 | qubership-apihub-nodejs-dev-image | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 46 | qubership-apihub-npm-gitflow | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 47 | qubership-apihub-postman-collections | qubership-apihub apihub |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 48 | qubership-apihub-protobufjs-research | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 49 | qubership-apihub-rest-playground | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 50 | qubership-apihub-sniffer-agent | qubership-apihub apihub |
✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 51 | qubership-apihub-test-service | qubership-apihub apihub |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 52 | qubership-apihub-traffic-analyzer | qubership-apihub apihub |
✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 53 | qubership-apihub-ui | qubership-apihub apihub, broadcast-pilot, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 54 | qubership-apihub-ui-tests | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 55 | qubership-apihub-vscode | qubership-apihub apihub, frontend |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 56 | qubership-av-scan-service | qubership-infra |
❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 57 | qubership-backup-daemon | qubership-infra saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 58 | qubership-cloud-passport-cli | qubership-devops |
✅ | ❌ | ❌ | 😱 | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ |
| 59 | qubership-colly | qubership-devops broadcast-pilot |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 60 | qubership-consul | qubership-devops consul, saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 61 | qubership-consul-acl-configurator | qubership-devops consul, saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 62 | qubership-consul-backup-daemon | qubership-devops consul, saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 63 | qubership-core-base-images | qubership-core base-image, core |
✅ | ✅ | ✅ | 😱 | ❌ | 😱 | ✅ | ✅ | 😱 | ✅ | ❌ |
| 64 | qubership-core-blue-green-state-monitor | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 65 | qubership-core-blue-green-state-monitor-quarkus | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 66 | qubership-core-bootstrap | qubership-core core |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 67 | qubership-core-config-server | qubership-core cloud-core, core, java, spring |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 68 | qubership-core-context-propagation | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 69 | qubership-core-context-propagation-quarkus | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 70 | qubership-core-control-plane | qubership-core cloud-core, core, go, service-mesh |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 71 | qubership-core-core-operator | qubership-core cloud-core, core, java, quarkus |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 72 | qubership-core-dbaas-agent | qubership-core cloud-core, core, go |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 73 | qubership-core-error-handling | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 74 | qubership-core-facade-operator | qubership-core cloud-core, core, go |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 75 | qubership-core-infra | qubership-core core |
❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 76 | qubership-core-ingress-gateway | qubership-core cloud-core, core, envoy, service-mesh |
✅ | ✅ | ✅ | 😱 | ❌ | 😱 | ❌ | ✅ | 😱 | ✅ | ❌ |
| 77 | qubership-core-junit-k8s-extension | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 78 | qubership-core-lib-go | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 79 | qubership-core-lib-go-actuator-common | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 80 | qubership-core-lib-go-bg-kafka | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 81 | qubership-core-lib-go-bg-state-monitor | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 82 | qubership-core-lib-go-dbaas-arangodb-client | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 83 | qubership-core-lib-go-dbaas-base-client | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 84 | qubership-core-lib-go-dbaas-cassandra-client | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 85 | qubership-core-lib-go-dbaas-clickhouse-client | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 86 | qubership-core-lib-go-dbaas-mongo-client | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 87 | qubership-core-lib-go-dbaas-opensearch-client | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 88 | qubership-core-lib-go-dbaas-postgres-client | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 89 | qubership-core-lib-go-error-handling | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 90 | qubership-core-lib-go-fiber-server-utils | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 91 | qubership-core-lib-go-maas-bg-segmentio | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 92 | qubership-core-lib-go-maas-client | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 93 | qubership-core-lib-go-maas-core | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 94 | qubership-core-lib-go-maas-segmentio | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 95 | qubership-core-lib-go-paas-mediation-client | qubership-core core, go, lib |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 96 | qubership-core-lib-go-rest-utils | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 97 | qubership-core-lib-go-stomp-websocket | qubership-core core, go, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 98 | qubership-core-maas-agent | qubership-core cloud-core, core, go |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 99 | qubership-core-microservice-dependencies | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 100 | qubership-core-microservice-framework | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 101 | qubership-core-microservice-framework-extensions | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 102 | qubership-core-mongo-evolution | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 103 | qubership-core-paas-mediation | qubership-core cloud-core, core, go |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 104 | qubership-core-process-orchestrator | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 105 | qubership-core-quarkus-extensions | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 106 | qubership-core-rest-libraries | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 107 | qubership-core-restclient | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 108 | qubership-core-site-management | qubership-core cloud-core, core, go |
✅ | ✅ | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ |
| 109 | qubership-core-springboot-starter | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 110 | qubership-core-utils | qubership-core core, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 111 | qubership-cql-driver | qubership-infra |
❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 112 | qubership-credential-manager | qubership-infra |
✅ | ✅ | ❌ | 😱 | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 113 | qubership-dbaas | qubership-core core, dbaas, java |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ |
| 114 | qubership-dbaas-adapter-core | qubership-core |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 115 | qubership-dbaas-client | qubership-core core, dbaas, java, lib |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 116 | qubership-deployment-status-provisioner | qubership-infra saqs |
✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 117 | qubership-diag-proxy | qubership-ossf-request observability, proxy |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 118 | qubership-disaster-recovery-daemon | qubership-infra k8sstream |
✅ | ✅ | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 119 | qubership-docker-integration-tests | qubership-infra saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 120 | qubership-docker-opensearch | qubership-infra opensearch, saqs |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 121 | qubership-env-checker | qubership-ossf-request observability |
⛅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 122 | qubership-envgene | qubership-devops |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 123 | qubership-envgene-instance | qubership-devops |
✅ | ❌ | 💤 | 💤 | ❌ | 💤 | ✅ | 💤 | 💤 | 💤 | 💤 |
| 124 | qubership-envgene-template | qubership-devops |
✅ | ❌ | 💤 | 💤 | ❌ | 💤 | ✅ | 💤 | 💤 | 💤 | 💤 |
| 125 | qubership-external-logging-installer | qubership-ossf-request logging, observability |
✅ | ❌ | ❌ | 😱 | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ |
| 126 | qubership-fluent-pipeline-tests | qubership-ossf-request logging, observability, testing |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 127 | qubership-fluentd | qubership-ossf-request logging, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 128 | qubership-git-system-follower | qubership-devops |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 129 | qubership-grafana-plugins-init | qubership-ossf-request monitoring, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 130 | qubership-grafana-reporter | qubership-ossf-request monitoring, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 131 | qubership-graphite-remote-adapter | qubership-ossf-request monitoring, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 132 | qubership-graylog-archiving-plugin | qubership-ossf-request logging, observability, plugin |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 133 | qubership-graylog-auth-proxy | qubership-ossf-request logging, observability, proxy |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 134 | qubership-graylog-obfuscation-plugin | qubership-ossf-request logging, observability, plugin |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 135 | qubership-graylog-plugins-init | qubership-ossf-request logging, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 136 | qubership-hive-metastore | qubership-infra |
✅ | ✅ | ❌ | 😱 | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 137 | qubership-hub-test | qubership-devops |
✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 138 | qubership-integration-catalog-library | qubership-integration broadcast-pilot, qip |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ |
| 139 | qubership-integration-checkstyle | qubership-integration qip |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 140 | qubership-integration-designtime-catalog | qubership-integration broadcast-pilot, qip |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ |
| 141 | qubership-integration-engine | qubership-integration broadcast-pilot, qip |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ |
| 142 | qubership-integration-platform | qubership-integration broadcast-pilot, qip |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 143 | qubership-integration-runtime-catalog | qubership-integration broadcast-pilot, qip |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ |
| 144 | qubership-integration-schemas | qubership-integration qip |
✅ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 145 | qubership-integration-sessions-management | qubership-integration broadcast-pilot, qip |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ |
| 146 | qubership-integration-ui | qubership-integration qip |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 147 | qubership-integration-variables-management | qubership-integration broadcast-pilot, qip |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ |
| 148 | qubership-inventory-tool-cli | qubership-ossf-request observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 149 | qubership-inventory-tool-core | qubership-ossf-request observability |
⛅ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 150 | qubership-jaeger | qubership-ossf-request broadcast-pilot, observability, tracing |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 151 | qubership-kafka | qubership-infra kafka, saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 152 | qubership-kube-events-generator | qubership-ossf-request logging, observability, testing |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 153 | qubership-kube-events-reader | qubership-ossf-request logging, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 154 | qubership-landscape-config | qubership-landscape |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 155 | qubership-landscape-config-processor | qubership-landscape |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 156 | qubership-log-exporter | qubership-ossf-request logging, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 157 | qubership-log-generator | qubership-ossf-request logging, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 158 | qubership-logging-operator | qubership-ossf-request logging, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 159 | qubership-maas | qubership-core core, go, maas |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 160 | qubership-maas-client | qubership-core core, java, lib, maas |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 161 | qubership-maas-client-quarkus | qubership-core core, java, lib, maas |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 162 | qubership-maas-client-spring | qubership-core core, java, lib, maas |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 163 | qubership-maas-declarative-client-commons | qubership-core core, java, lib, maas |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 164 | qubership-maas-declarative-client-quarkus | qubership-core core, java, lib, maas |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 165 | qubership-maas-declarative-client-spring | qubership-core core, java, lib, maas |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 166 | qubership-mistral | qubership-infra |
✅ | ✅ | ❌ | 😱 | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 167 | qubership-mistral-operator | qubership-infra |
✅ | ✅ | ❌ | 😱 | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 168 | qubership-mongodb-driver | qubership-infra |
❌ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 169 | qubership-monitoring-operator | qubership-ossf-request monitoring, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 170 | qubership-network-latency-exporter | qubership-ossf-request monitoring, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 171 | qubership-nifi | qubership-nifi nifi |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 172 | qubership-nifi-registry | qubership-nifi nifi-registry |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 173 | qubership-nosqldb-operator-core | qubership-infra |
❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 174 | qubership-observability-examples | qubership-observability examples, observability |
✅ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 175 | qubership-observability-operator | qubership-observability observability |
✅ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 176 | qubership-open-telemetry-collector | qubership-ossf-request observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 177 | qubership-opensearch | qubership-infra opensearch, saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 178 | qubership-opensearch-curator | qubership-infra opensearch, saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 179 | qubership-opensearch-dbaas-adapter | qubership-infra opensearch, saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 180 | qubership-opensearch-monitoring | qubership-infra opensearch, saqs |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 181 | qubership-opentelemetry-helm-charts | qubership-observability observability |
✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 182 | qubership-pipelines-cli-command-samples | qubership-devops |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 183 | qubership-pipelines-common-python-library | qubership-devops |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 184 | qubership-pipelines-declarative-executor | qubership-devops |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 185 | qubership-pipelines-modules-ops | qubership-devops |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 186 | qubership-profiler-agent | qubership-ossf-request broadcast-pilot, observability, profiler |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 187 | qubership-prometheus-adapter-operator | qubership-ossf-request monitoring, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 188 | qubership-query-exporter | qubership-infra |
✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 189 | qubership-renovate-config | qubership-devops |
❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 190 | qubership-repo-template | qubership-devops |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 191 | qubership-spark-on-k8s | qubership-infra |
✅ | ✅ | ❌ | 😱 | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 192 | qubership-tcp-duplicator | qubership-ossf-request logging, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 193 | qubership-test-pipelines | qubership-devops |
❌ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 194 | qubership-testing-platform-adapter-robot-library | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 195 | qubership-testing-platform-auth-library | qubership-tp |
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 196 | qubership-testing-platform-common-auditing-library | qubership-tp |
⛅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 197 | qubership-testing-platform-common-library | qubership-tp |
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 198 | qubership-testing-platform-configuration-dataset-excel-library | qubership-tp |
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 199 | qubership-testing-platform-crypt-library | qubership-tp |
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 200 | qubership-testing-platform-datasets | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 201 | qubership-testing-platform-diameter-transport-library | qubership-tp |
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 202 | qubership-testing-platform-environments | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 203 | qubership-testing-platform-export-import-library | qubership-tp |
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 204 | qubership-testing-platform-integration-library | qubership-tp |
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 205 | qubership-testing-platform-itf-core-library | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 206 | qubership-testing-platform-itf-executor | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 207 | qubership-testing-platform-itf-lite-backend | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 208 | qubership-testing-platform-itf-reporting | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 209 | qubership-testing-platform-itf-stubs | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 210 | qubership-testing-platform-macros-core-library | qubership-tp |
⛅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 211 | qubership-testing-platform-multitenancy-library | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 212 | qubership-testing-platform-ram | qubership-tp |
✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 213 | qubership-testing-platform-ss7-transport-library | qubership-tp |
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 214 | qubership-trino | qubership-infra |
✅ | ✅ | ❌ | 😱 | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 215 | qubership-version-exporter | qubership-ossf-request monitoring, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
| 216 | qubership-workflow-hub | qubership-devops |
⛅ | ✅ | ❌ | 😱 | ✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ✅ |
| 217 | qubership-zookeeper | qubership-infra saqs, zookeeper |
✅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 218 | release-drafter | qubership-devops |
⛅ | ✅ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ |
| 219 | robot-shop | qubership-observability example, observability |
✅ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ |
| # | ID | Team | CNCF Status | CNCF Category | CNCF Subcategory | GenAI Alternatives | GenAI Notes |
|---|---|---|---|---|---|---|---|
| 1 | .github | qubership-devops |
❌ | ⛅ | ⛅ | ⛅ | |
| 2 | KubeMarine | qubership-infra administration, devops, helm, k8sstream, kubernetes |
✅ | Provisioning | Cluster Management | kops, kubespray, Rancher, Cluster API | Kubemarine is described as a lightweight and powerful management tool for end-to-end Kubernetes cluster deployment and maintenance. It provides CLI commands and can be customized using a Python extension API. It supports various deployment schemes (all-in-one, mini-HA, HA, etc.) and can be used for both deployment and maintenance stages. This aligns with the 'Provisioning' category in the CNCF landscape, specifically under 'Cluster Management', as it focuses on setting up and managing Kubernetes clusters. Alternatives like kops, kubespray, Rancher, and Cluster API are also tools in the same space, providing similar functionalities for Kubernetes cluster provisioning and management. |
| 3 | base-images-module-base | qubership-infra base-image |
❌ | n/a ❌ | n/a ❌ | The provided base64 content 'IyBiYXNlLWltYWdlcy1tb2R1bGUtYmFzZQ==' decodes to '# base-images-module-base', which is insufficient to determine the category or subcategory of the solution within the CNCF landscape. No meaningful description or context was provided to analyze the solution's purpose, functionality, or its relation to CNCF categories. Therefore, all fields are marked as 'n/a' or empty where applicable. | |
| 4 | cassandra | ❌ | ❌ | ⛅ | ⛅ | ⛅ | |
| 5 | cassandra-exporter | qubership-infra |
✅ | Monitoring | Metrics | jmx_exporter, kube-state-metrics, node_exporter | The cassandra-exporter is a Java agent that exports Cassandra metrics to Prometheus, which is a common use case in the Monitoring category of the CNCF landscape. It follows Prometheus best practices for metric naming and labeling. Alternatives like jmx_exporter also export JVM and application metrics to Prometheus, while kube-state-metrics and node_exporter focus on Kubernetes and node metrics respectively. The cassandra-exporter is specifically tailored for Cassandra, making it a specialized tool in the Metrics subcategory. |
| 6 | chart-releaser-action | qubership-devops |
❌ | ⛅ | ⛅ | ⛅ | |
| 7 | cla-storage | qubership-infra |
❌ | n/a ❌ | n/a ❌ | The provided base64 content 'IyBjbGEtc3RvcmFnZQ==' decodes to '# cla-storage', which is insufficient to determine the category or subcategory within the CNCF landscape. More context or a detailed description of the solution is needed to make an accurate classification and suggest alternatives. | |
| 8 | gatekeeper-library | qubership-infra |
✅ | App Definition and Development | Documentation | VuePress, MkDocs, Hugo | The provided content describes a website built using Docusaurus 2, which is a modern static website generator primarily used for documentation. Docusaurus falls under the 'App Definition and Development' category in the CNCF landscape, specifically under the 'Documentation' subcategory, as it is a tool designed to create and maintain documentation websites. Alternatives like VuePress, MkDocs, and Hugo are also static site generators commonly used for documentation purposes, making them suitable alternatives within the same CNCF category. |
| 9 | get-package-ids | qubership-infra |
✅ | App Definition and Development | CI/CD | Tekton, Argo Workflows, Jenkins X | The provided file describes a GitHub Action that finds package IDs for specific Docker images, which is a task related to CI/CD workflows. The action is defined in a YAML file, which is typical for CI/CD tools. The alternatives listed are other CI/CD tools within the CNCF landscape that also focus on automating workflows and integrating with containerized environments. |
| 10 | k8s-conformance | qubership-infra |
✅ | App Definition and Development | Container Runtime | containerd, CRI-O, Kata Containers | The provided file describes a cloud-native platform based on Kubernetes, focusing on container runtime and orchestration. The commands and procedures mentioned are related to initializing and joining Kubernetes nodes, running conformance tests, and managing containerized applications. This aligns with the 'Container Runtime' subcategory under 'App Definition and Development' in the CNCF landscape. Alternatives like containerd, CRI-O, and Kata Containers are other container runtimes that are part of the CNCF ecosystem and serve similar purposes. |
| 11 | kafka | ❌ | ❌ | ⛅ | ⛅ | ⛅ | |
| 12 | keycloak | ❌ | ❌ | ⛅ | ⛅ | ⛅ | |
| 13 | microservice-restclient | qubership-infra |
✅ | App Definition and Development | Microservice Tools | gRPC, Istio, Linkerd | The provided file decodes to 'microservice-restclient', which suggests it is related to microservices and REST clients. This fits well under the 'App Definition and Development' category in the CNCF landscape, specifically under 'Microservice Tools'. Alternatives like gRPC, Istio, and Linkerd are also part of the CNCF landscape and are commonly used for microservice communication and management, making them relevant alternatives. |
| 14 | pg_hint_plan | qubership-infra |
✅ | Database | Query Optimization | Vitess, TiDB, CockroachDB | The provided file describes 'pg_hint_plan', a PostgreSQL extension that allows tweaking execution plans using hints in SQL comments. This fits under the 'Database' category in the CNCF landscape, specifically under 'Query Optimization'. Alternatives like Vitess, TiDB, and CockroachDB also offer advanced query optimization features and are part of the CNCF landscape. |
| 15 | pgskipper-backup-daemon | qubership-infra |
✅ | Database | Backup and Recovery | Velero, KubeDB, Stash | The solution described is focused on periodic backups and recovery of PostgreSQL databases, which aligns with the 'Backup and Recovery' subcategory under 'Database' in the CNCF landscape. Similar solutions in the CNCF landscape include Velero (for general backup and recovery), KubeDB (for database management including backups), and Stash (for backup and recovery of Kubernetes workloads). The description mentions the ability to run backups periodically and recover databases, which is a core functionality of backup and recovery tools. |
| 16 | pgskipper-dbaas-adapter | qubership-infra |
❌ | Database | n/a ❌ | Vitess, TiDB, CockroachDB | The provided file describes a component that offers a REST API for logical database management, which aligns with the Database category in the CNCF landscape. The component appears to be a database adapter or middleware, which is why alternatives like Vitess, TiDB, and CockroachDB are suggested as they also provide database management capabilities. However, the subcategory is not specified due to insufficient details about the specific type of database management (e.g., SQL, NoSQL, distributed). |
| 17 | pgskipper-monitoring-agent | qubership-infra |
❌ | Monitoring | n/a ❌ | Prometheus, Thanos, VictoriaMetrics | The name 'pgskipper-monitoring-agent' suggests that this is a monitoring agent, likely for PostgreSQL (given the 'pg' prefix). Since monitoring agents fall under the 'Monitoring' category in the CNCF landscape, this seems to be the best fit. Alternatives like Prometheus, Thanos, and VictoriaMetrics are also monitoring solutions in the CNCF ecosystem, though they are more general-purpose compared to what appears to be a PostgreSQL-specific agent. |
| 18 | pgskipper-operator | qubership-infra |
✅ | Database | SQL Database | vitess, CloudNativePG, RadonDB PostgreSQL | The provided file describes 'Postgres-Operator', which is a solution for running PostgreSQL as a service on Kubernetes and OpenShift. This clearly falls under the 'Database' category in the CNCF landscape, specifically under 'SQL Database' subcategory as PostgreSQL is a relational database. Alternatives like 'vitess', 'CloudNativePG', and 'RadonDB PostgreSQL' are also CNCF-listed projects that provide similar functionalities for managing PostgreSQL databases in cloud-native environments. |
| 19 | pgskipper-operator-core | qubership-infra |
❌ | n/a ❌ | n/a ❌ | n/a ❌ | The provided base64 content decodes to '# pgskipper-operator-core', which is insufficient to determine the category or subcategory within the CNCF landscape. More context or description about the solution's functionality, purpose, and use cases is needed to make an accurate classification. |
| 20 | pgskipper-patroni | qubership-infra |
❌ | n/a ❌ | n/a ❌ | The provided base64 content decodes to '# pgskipper-patroni', which appears to be a very brief and unclear description. It might refer to a combination of 'pgskipper' (possibly related to PostgreSQL) and 'Patroni' (a popular tool for managing PostgreSQL high availability). However, without more context or details about the solution's functionality, components, or purpose, it is impossible to accurately categorize it within the CNCF landscape or suggest alternatives. More information is needed to make a proper classification. | |
| 21 | pgskipper-pgbackrest-sidecar | qubership-infra |
❌ | n/a ❌ | n/a ❌ | The provided content is insufficient to determine the category or subcategory within the CNCF landscape. The text appears to be a filename or a fragment without meaningful context about the solution's functionality, purpose, or components. More information is required to make an accurate classification. | |
| 22 | pgskipper-replication-controller | qubership-infra |
✅ | Database | Replication | Vitess, TiDB, YugabyteDB | The provided file describes a component that offers a REST API for managing PostgreSQL publications, which is related to database replication. This functionality aligns with the 'Database' category in the CNCF landscape, specifically under the 'Replication' subcategory. Alternatives like Vitess, TiDB, and YugabyteDB are included as they also provide solutions for database replication and management within the CNCF ecosystem. |
| 23 | pgskipper-upgrade | qubership-infra |
❌ | n/a ❌ | n/a ❌ | The provided base64 content decodes to '# pgskipper-upgrade', which is insufficient to determine the category or subcategory within the CNCF landscape. More context or description about the solution is needed to make an accurate classification. | |
| 24 | postgres | ❌ | ❌ | ⛅ | ⛅ | ⛅ | |
| 25 | qubership-airflow | qubership-infra |
❌ | ⛅ | ⛅ | ⛅ | |
| 26 | qubership-api-linter-service | qubership-apihub apihub |
✅ | App Definition and Development | API Gateway | Kong, Traefik, Envoy | The provided file describes a Golang microservice that provides a REST API for linting OAS (OpenAPI Specification) files. This functionality is typically associated with API gateways or API management tools, which fall under the 'App Definition and Development' category in the CNCF landscape. The subcategory 'API Gateway' is chosen because the service seems to focus on API-related operations. Alternatives like Kong, Traefik, and Envoy are listed as they are prominent CNCF projects in the API Gateway space. The note about the project being under development and not production-ready suggests that it's an early-stage tool, but the described functionality aligns well with API gateway services. |
| 27 | qubership-apihub | qubership-apihub apihub |
✅ | App Definition and Development | Application Definition & Image Build | Helm, Kustomize, Tanka | The provided file describes a Helm chart for deploying Qubership APIHUB to a Kubernetes cluster. Helm is a package manager for Kubernetes, which falls under the 'App Definition and Development' category in the CNCF landscape, specifically under 'Application Definition & Image Build'. Alternatives like Kustomize and Tanka are also tools for managing Kubernetes applications, making them relevant alternatives. The mention of Helm charts and Kubernetes deployment strongly suggests this categorization. |
| 28 | qubership-apihub-agent | qubership-apihub apihub |
✅ | App Definition and Development | API Gateway | Kong, Traefik, Envoy, Gloo | The provided file describes a Helm chart for deploying the QuberShip APIHUB Agent to a Kubernetes cluster. The solution is focused on API management and gateway functionality, which aligns with the 'App Definition and Development' category in the CNCF landscape, specifically under 'API Gateway'. Alternatives like Kong, Traefik, Envoy, and Gloo are also API gateways that provide similar functionality and are part of the CNCF landscape. The file mentions Kubernetes as a mandatory dependency, which further supports the classification under cloud-native technologies. |
| 29 | qubership-apihub-api-data-model | qubership-apihub apihub, frontend |
✅ | App Definition and Development | API Gateway | Kong, Apigee, Tyk | The description mentions converting JSON schema-based documents into a structured and simplified data tree, which is a common feature of API gateways that transform and manage API data. The modified version of 'udamir/api-model-tree' suggests it's related to API data modeling. The alternatives listed are popular API gateways in the CNCF landscape that provide similar functionality. |
| 30 | qubership-apihub-api-diff | qubership-apihub apihub, frontend |
✅ | App Definition and Development | API Gateway | Kong, Envoy, Apigee, Tyk | The provided file describes a tool for generating API diffs, changelogs, and ensuring API versioning consistency, which aligns with the functionality of API gateways and management tools in the CNCF landscape. The tool supports various API specifications like OpenAPI, AsyncAPI, and JSON Schema, which are commonly handled by API gateways. The alternatives listed are popular API gateways and management tools within the CNCF ecosystem that provide similar functionalities. |
| 31 | qubership-apihub-api-doc-viewer | qubership-apihub apihub, frontend |
✅ | App Definition and Development | API Gateway | Apollo GraphQL, GraphQL Playground, GraphiQL, Swagger UI | The provided solution is a library that renders JSON schemas, GraphQL schemas, and GraphAPI specifications in a human-readable way. It provides components like GraphQLOperationViewer and JsonSchemaViewer, which are used to visualize and interact with API schemas. This functionality is similar to tools like Apollo GraphQL, GraphQL Playground, GraphiQL, and Swagger UI, which are used for API documentation and exploration. These tools fall under the 'App Definition and Development' category in the CNCF landscape, specifically under 'API Gateway' as they facilitate API interaction and documentation. |
| 32 | qubership-apihub-api-processor | qubership-apihub apihub, broadcast-pilot, frontend |
✅ | API Gateway | API Management | Kong, Envoy, Apigee, Tyk | The solution described in the file focuses on unifying and normalizing API presentations, supporting OpenAPI and GraphQL specifications, and providing features like schema merging, reference resolution, and custom rules for document types. These functionalities align closely with the API Gateway and API Management categories in the CNCF landscape. The solution's emphasis on processing different API specifications, merging schemas, and supporting various API formats (like OpenAPI and GraphQL) makes it a fit for API Management tools. Alternatives like Kong, Envoy, Apigee, and Tyk are listed as they provide similar capabilities in API gateway and management, including support for OpenAPI and GraphQL, schema validation, and API unification. |
| 33 | qubership-apihub-api-unifier | qubership-apihub apihub, frontend |
✅ | API Infrastructure | API Gateway | Kong, Envoy, Gloo | The solution described in the file is focused on unifying APIs into a normalized presentation with support for OpenAPI and GraphQL specifications. It also mentions features like schema merging, reference resolution, and support for various API specifications, which are common in API Gateway solutions. The CNCF landscape categorizes API Gateways under 'API Infrastructure', and popular alternatives in this space include Kong, Envoy, and Gloo, which also provide API unification, transformation, and routing capabilities. |
| 34 | qubership-apihub-api-visitor | qubership-apihub apihub, frontend |
✅ | API Gateway | API Tools | Apigee, Kong, Tyk | The provided file describes a utility for type-safe OpenAPI specification crawling, which is related to API tools. The mention of 'schema object' and 'self loops' suggests it's used for analyzing and validating API specifications, a common feature in API Gateway and API tooling solutions. The alternatives listed are other CNCF projects or popular tools in the API Gateway space that provide similar functionality for API specification handling and validation. |
| 35 | qubership-apihub-apispec-view | qubership-apihub apihub, frontend |
✅ | App Definition and Development | Documentation | Docusaurus, VuePress, Docsify | The provided file describes a collection of UI components for displaying beautiful developer documentation from any OpenAPI document. This aligns with the 'App Definition and Development' category in the CNCF landscape, specifically under the 'Documentation' subcategory, as it focuses on tools that help developers create and maintain documentation. Alternatives like Docusaurus, VuePress, and Docsify are also documentation tools that help developers create and maintain documentation sites, making them suitable alternatives. |
| 36 | qubership-apihub-backend | qubership-apihub apihub, broadcast-pilot |
❌ | n/a ❌ | n/a ❌ | The provided file describes 'ot' as a minimal operational-transformation library for collaborative editing, originally derived from a GitHub project. However, the description does not provide enough information to clearly categorize it within the CNCF landscape. CNCF primarily focuses on cloud-native technologies like container orchestration, service meshes, monitoring, and storage solutions, whereas 'ot' seems to be a library for collaborative text editing, which doesn't directly align with any CNCF category. Therefore, no suitable alternatives from the CNCF landscape could be identified. | |
| 37 | qubership-apihub-build-task-consumer | qubership-apihub apihub, frontend |
✅ | App Definition and Development | Microservices | Express, Fastify, Koa | The provided file describes a Node.js microservice for APIHub Package versions builds. It includes installation, building, running, and testing the application, which aligns with the 'App Definition and Development' category in the CNCF landscape. The 'Microservices' subcategory is chosen because the solution is a small, focused service for a specific task. Alternatives like Express, Fastify, and Koa are listed as they are also Node.js frameworks commonly used for building microservices. |
| 38 | qubership-apihub-ci | qubership-apihub apihub |
✅ | App Definition and Development | API Gateway | Kong, Traefik, Envoy | The file name 'qubernetes-apihub-ci' suggests a Kubernetes-related tool with API capabilities, likely an API gateway or management solution. Given the limited information, it's categorized under 'App Definition and Development' with a subcategory of 'API Gateway'. Alternatives like Kong, Traefik, and Envoy are popular CNCF projects in this space. |
| 39 | qubership-apihub-class-view | qubership-apihub apihub, frontend |
✅ | App Definition and Development | Application Definition & Image Build | Backstage, KubeVela, OAM | The provided description mentions a tool that provides a UML class diagram-like representation of entities and relations, which is typically used in application definition and development. The features like auto-layout, transitions animation, selection, tooltip, and navigate to are common in tools that help visualize and manage application components. Alternatives like Backstage, KubeVela, and OAM are also focused on application definition and development, providing similar capabilities for visualizing and managing application components. |
| 40 | qubership-apihub-compatibility-suites | qubership-apihub apihub, frontend |
✅ | App Definition and Development | API Gateway | Kong, Apigee, Tyk | The provided file describes a solution focused on API compatibility and changes classification, specifically mentioning OpenAPI and GraphQL. This aligns with the 'API Gateway' subcategory under 'App Definition and Development' in the CNCF landscape. The solution provides tools for managing and testing API changes, which is a core functionality of API gateways. Alternatives like Kong, Apigee, and Tyk are listed as they offer similar API management and testing capabilities. |
| 41 | qubership-apihub-graphapi | qubership-apihub apihub, frontend |
✅ | API Gateway | GraphQL Tools | Apollo Server, GraphQL Mesh, Hasura | The provided file describes a package that provides utilities to convert GraphQL schema into GraphAPI document and back, which is a tool for working with GraphQL APIs. This aligns with the CNCF category of API Gateway, specifically under GraphQL Tools, as it facilitates the management and transformation of GraphQL schemas. Alternatives like Apollo Server, GraphQL Mesh, and Hasura are also part of the CNCF landscape and provide similar functionalities for GraphQL schema management and API gateway services. |
| 42 | qubership-apihub-http-spec | qubership-apihub apihub, frontend |
✅ | API Infrastructure | API Specifications | Swagger, Apicurio, Kusk | The provided file describes a converter for OpenAPI schemas to JSON schemas, which is a tool used in API development and specification management. This fits under the 'API Infrastructure' category in the CNCF landscape, specifically under 'API Specifications' as it deals with schema conversion and management. Alternatives like Swagger, Apicurio, and Kusk are also tools that handle API specifications and transformations, making them relevant alternatives. |
| 43 | qubership-apihub-jest-chrome-in-docker-environment | qubership-apihub apihub, frontend |
✅ | Testing | Browser Testing | Selenium, Cypress, TestCafe, Playwright | The described solution is focused on running Chrome browser in identical environments across different machines, including CI and local PCs, for screenshot tests. It leverages Docker to ensure consistency and simplifies interactions with Docker and Chrome. This aligns with the 'Testing' category in the CNCF landscape, specifically under 'Browser Testing' subcategory. Alternatives like Selenium, Cypress, TestCafe, and Playwright are also tools designed for browser automation and testing, making them suitable comparisons. |
| 44 | qubership-apihub-json-crawl | qubership-apihub apihub, frontend |
❌ | n/a ❌ | n/a ❌ | The provided file describes a utility package for crawling/cloning JSON objects in a tree-like structure, which is a development tool rather than a cloud-native solution. The CNCF landscape primarily focuses on cloud-native technologies like container orchestration, service meshes, monitoring, etc. This package does not fit into any specific CNCF category as it is a general-purpose library for JSON manipulation. Therefore, no direct alternatives from the CNCF landscape are applicable. | |
| 45 | qubership-apihub-nodejs-dev-image | qubership-apihub apihub, frontend |
❌ | App Definition and Development | Development Environment | n/a ❌ | The provided content describes a development environment setup with tools like Node, NPM, Yarn, Chrome, and Puppeteer. This fits best under the 'App Definition and Development' category in the CNCF landscape, specifically under 'Development Environment'. However, the description lacks specific details about a particular CNCF project or framework, so no direct alternatives are provided. The tools listed are common for local development rather than cloud-native tools, which might explain the lack of direct alternatives in the CNCF landscape. |
| 46 | qubership-apihub-npm-gitflow | qubership-apihub apihub, frontend |
✅ | App Definition and Development | Package Management | Lerna, Yarn, Rush | The provided file describes a tool that automates common gitflow processes for NPM repositories, manages git branches according to a specific branching model, and updates versions for NPM and Lerna projects. This functionality is closely related to package management and development workflow automation, which falls under the 'App Definition and Development' category in the CNCF landscape. The subcategory 'Package Management' is chosen because the tool specifically deals with NPM and Lerna projects. Alternatives like Lerna, Yarn, and Rush are listed as they are also tools that manage dependencies and workflows in JavaScript/TypeScript projects. |
| 47 | qubership-apihub-postman-collections | qubership-apihub apihub |
✅ | App Definition and Development | API Gateway | Kong, Apigee, Tyk | The provided content describes a solution for managing API keys, creating test data, and handling API requests, which aligns with the functionality of an API Gateway. The mention of 'apihub' and the process of creating API keys and managing access suggests a tool focused on API management. The alternatives listed are other well-known API gateways in the CNCF landscape that provide similar capabilities. |
| 48 | qubership-apihub-protobufjs-research | qubership-apihub apihub, frontend |
✅ | App Definition and Development | API Gateway | Kong, Envoy, Linkerd | The provided file discusses the use of JSON descriptors for processing proto files in an APIHUB context, which suggests a focus on API management and development. The Cloud Native Computing Foundation (CNCF) landscape categorizes API gateways under 'App Definition and Development'. The alternatives listed (Kong, Envoy, Linkerd) are well-known API gateways and service mesh solutions within the CNCF landscape that handle API management and development tasks similar to what is described in the file. The file's emphasis on proto file processing and conversion aligns with the capabilities of these tools. |
| 49 | qubership-apihub-rest-playground | qubership-apihub apihub, frontend |
✅ | App Definition and Development | API Gateway | Kong, Traefik, Envoy | The provided base64 content mentions 'qubership-apihub-rest-playground' and a fork of 'elements' from stoplightio, which is related to API development and tooling. This suggests the solution is likely an API gateway or API development framework. The CNCF landscape categorizes API gateways under 'App Definition and Development'. Alternatives like Kong, Traefik, and Envoy are well-known API gateways in the CNCF landscape that fit this category. |
| 50 | qubership-apihub-sniffer-agent | qubership-apihub apihub |
❌ | n/a ❌ | n/a ❌ | The provided content describes a folder containing public data types and constants for interacting with external systems and users, but it does not provide enough information to determine a specific category or subcategory within the CNCF landscape. The files mentioned (e.g., CallResult.go, CaptureRequest.go, Constants.go) suggest a focus on data types and constants, but without more context about the framework or application they belong to, it's impossible to accurately classify them. Therefore, all fields are marked as 'n/a'. | |
| 51 | qubership-apihub-test-service | qubership-apihub apihub |
❌ | API Gateway | n/a ❌ | Kong, Traefik, Envoy | The description mentions a microservice that exposes various API specifications (REST, GraphQL, Async, etc.) on various endpoints, which aligns with the functionality of an API Gateway. The solution is used for testing needs in the context of Quibership-APIHUB, suggesting it acts as a central point for API management. Alternatives like Kong, Traefik, and Envoy are listed as they are prominent API Gateway solutions in the CNCF landscape. |
| 52 | qubership-apihub-traffic-analyzer | qubership-apihub apihub |
❌ | n/a ❌ | n/a ❌ | n/a ❌ | The provided file describes utility code for helper functions (goroutines, hashing, UUID generation) but does not provide enough context to determine a specific CNCF category. Utility code alone is too generic to classify within the CNCF landscape, which focuses on cloud-native tools, platforms, and frameworks. No cloud-native or distributed system components are mentioned. |
| 53 | qubership-apihub-ui | qubership-apihub apihub, broadcast-pilot, frontend |
✅ | API Infrastructure | API Documentation | Swagger UI, Redoc, Stoplight | The solution described, APIHUB, is focused on API documentation, design, and validation, which aligns with the 'API Infrastructure' category in the CNCF landscape. It specifically falls under the 'API Documentation' subcategory as it provides tools for managing and viewing API specifications, similar to other solutions like Swagger UI, Redoc, and Stoplight. These alternatives also offer comprehensive API documentation and design features, making them suitable comparisons. |
| 54 | qubership-apihub-ui-tests | qubership-apihub apihub, frontend |
✅ | App Definition and Development | Testing | Selenium, Cypress, TestCafe | The provided file describes a project used for creating and running auto-tests, primarily for UI E2E (End-to-End) testing, using the Playwright framework. This fits well under the 'Testing' subcategory of 'App Definition and Development' in the CNCF landscape. Alternatives like Selenium, Cypress, and TestCafe are also popular tools in this space for UI automation testing. |
| 55 | qubership-apihub-vscode | qubership-apihub apihub, frontend |
✅ | App Definition and Development | API Gateway | Kong, Apigee, Tyk | The solution described is an extension for Quberchip that allows publishing API specifications and related documents to APIHUB. This functionality aligns with the 'API Gateway' subcategory under 'App Definition and Development' in the CNCF landscape. The solution focuses on API documentation and publishing, which is a core feature of API gateways. Alternatives like Kong, Apigee, and Tyk are listed as they provide similar API management and documentation features. |
| 56 | qubership-av-scan-service | qubership-infra |
✅ | Security | Scanning & Vulnerability | Clair, Trivy, Anchore Engine | The provided file describes an antivirus scan service that scans files for viruses using an HTTP API. This functionality aligns with the 'Scanning & Vulnerability' subcategory under the 'Security' category in the CNCF landscape. Similar projects in this space include Clair, Trivy, and Anchore Engine, which are also focused on scanning for vulnerabilities and security threats. |
| 57 | qubership-backup-daemon | qubership-infra saqs |
✅ | Storage | Backup & Restore | Velero, Kasten K10, Stash | The solution described in the file is primarily focused on backup and restore operations for databases like MongoDB and PostgreSQL. It provides a REST API for scheduling and managing backups, supports S3 storage, and includes features like eviction policies, custom variables, and granular backup options. These characteristics align well with the 'Backup & Restore' subcategory under 'Storage' in the CNCF landscape. Alternatives like Velero, Kasten K10, and Stash are also backup solutions that fit similar use cases within the CNCF ecosystem. |
| 58 | qubership-cloud-passport-cli | qubership-devops |
✅ | App Definition and Development | API Gateway | Kong, Envoy, Traefik | The provided file describes an open-source Python library used by QuberShip Cloud pass-port module, which appears to be a client library for interacting with a cloud service. Given that it's a client library, it's likely related to API interaction or gateway functionality. The alternatives listed (Kong, Envoy, Traefik) are all CNCF-listed projects that provide API gateway functionality, which seems to be the closest match to the described solution. However, the description is somewhat limited, so there's a degree of uncertainty in this categorization. |
| 59 | qubership-colly | qubership-devops broadcast-pilot |
✅ | App Definition and Development | Application Configuration | KubeVela, Crossplane, Helm | The project described, 'qubership-colly', is focused on tracking the usage of clusters and environments within clusters, supporting multiple clusters, grouping namespaces into environments, and displaying custom UI parameters. It also aims to collect resources and metrics from Kubernetes and monitoring. These functionalities align with the 'App Definition and Development' category in the CNCF landscape, specifically under 'Application Configuration', as it deals with managing and configuring applications within Kubernetes environments. Alternatives like KubeVela, Crossplane, and Helm are also focused on application configuration and management within Kubernetes, making them suitable alternatives. |
| 60 | qubership-consul | qubership-devops consul, saqs |
❌ | n/a ❌ | n/a ❌ | n/a ❌ | The provided content is insufficient to determine the specific CNCF category or subcategory for the Robot Framework. The description only mentions the usage of integration tests based on Robot Framework, but does not provide enough details about its functionality, architecture, or use cases to align it with a specific CNCF category. Additionally, no similar alternatives from the CNCF landscape can be identified based on the given information. |
| 61 | qubership-consul-acl-configurator | qubership-devops consul, saqs |
✅ | Security and Compliance | Identity and Access Management (IAM) | Hashicorp Vault, SPIFFE/SPIRE, Keycloak, Dex | The provided file describes a solution that manages Consul ACL policies, roles, and rule bindings through Kubernetes custom resources. This functionality is primarily focused on access control and identity management within a cloud-native environment, which aligns with the 'Security and Compliance' category in the CNCF landscape. Specifically, it falls under 'Identity and Access Management (IAM)' as it deals with defining and enforcing access policies for services. Alternatives like Hashicorp Vault, SPIFFE/SPIRE, Keycloak, and Dex are listed because they also provide IAM capabilities, including policy management, role-based access control (RBAC), and service-to-service authentication. The solution's integration with Kubernetes and Consul further supports its classification in this category. |
| 62 | qubership-consul-backup-daemon | qubership-devops consul, saqs |
✅ | Management and Governance | Backup and Recovery | Velero, Kasten K10, Stash | The provided file describes a backup and recovery solution for Consul Service, which includes features like full manual backup, granular backup, and non-evictable backup options. It also provides API-based operations for backup and recovery, status checks, and backup management. This aligns well with the 'Backup and Recovery' subcategory under 'Management and Governance' in the CNCF landscape. Alternatives like Velero, Kasten K10, and Stash are also popular backup and recovery solutions in the CNCF ecosystem that offer similar functionalities for cloud-native applications. |
| 63 | qubership-core-base-images | qubership-core base-image, core |
✅ | App Definition and Development | Container Images | Distroless, Alpine Linux, Red Hat Universal Base Image (UBI) | The provided file describes a set of secure and feature-rich Alpine Linux-based container images designed for containerized applications. These images include pre-configured security settings, certificate management, user management, and initialization script support. The focus on minimalism, security, and flexibility aligns well with the 'Container Images' subcategory under 'App Definition and Development' in the CNCF landscape. Alternatives like Distroless, Alpine Linux, and Red Hat UBI are also minimal, secure base images commonly used in cloud-native environments. |
| 64 | qubership-core-blue-green-state-monitor | qubership-core core, java, lib |
✅ | App Definition and Development | Application Configuration | Spring Cloud Config, Consul, etcd | The provided file describes a Spring Boot library for configuration and state monitoring, specifically mentioning integration with Consul for configuration management. This aligns with the 'App Definition and Development' category in the CNCF landscape, particularly under 'Application Configuration' subcategory, where tools like Spring Cloud Config, Consul, and etcd are commonly used for managing application configurations in cloud-native environments. The library's focus on configuration and state publishing suggests it fits best in this category. |
| 65 | qubership-core-blue-green-state-monitor-quarkus | qubership-core core, java, lib |
✅ | App Definition and Development | Microservice Tools | Spring Cloud, Micronaut, Quarkus | The provided file describes a library that integrates with Quarkus to provide configuration and state management for microservices, specifically mentioning features like BlueGreenStatePublisher and MicroserviceMutexService. This aligns with the 'App Definition and Development' category in the CNCF landscape, under 'Microservice Tools'. Alternatives like Spring Cloud, Micronaut, and Quarkus are listed as they are also frameworks that provide similar microservice tooling and integration capabilities. |
| 66 | qubership-core-bootstrap | qubership-core core |
❌ | ⛅ | ⛅ | ⛅ | |
| 67 | qubership-core-config-server | qubership-core cloud-core, core, java, spring |
❌ | ⛅ | ⛅ | ⛅ | |
| 68 | qubership-core-context-propagation | qubership-core core, java, lib |
✅ | Observability and Analysis | Tracing | OpenTelemetry, Jaeger, Zipkin | The solution described in the file is a context propagation framework designed to propagate values (such as headers, API versions, request IDs, etc.) between microservices. This functionality is crucial for distributed tracing, which is a key aspect of observability in cloud-native applications. The framework supports various propagation methods (REST, messaging) and integrates with Spring, Kafka, and RabbitMQ, similar to how OpenTelemetry, Jaeger, and Zipkin handle context propagation for tracing purposes. The solution fits best under the 'Observability and Analysis' category in the CNCF landscape, specifically under 'Tracing', as it provides the necessary tools to track and propagate context across service boundaries, which is essential for distributed tracing. |
| 69 | qubership-core-context-propagation-quarkus | qubership-core core, java, lib |
✅ | App Definition and Development | Application Framework | Spring Cloud, Micronaut, Quarkus, Helidon | The provided file describes a context propagation framework designed for microservices, which allows propagating values from one microservice to another. It supports various propagation methods (REST to REST, REST to Messaging, Messaging to REST, Messaging to Messaging) and includes features for working with context, such as propagating contexts to other threads, creating snapshots, and activating them later. This functionality aligns with application frameworks in the CNCF landscape, which provide tools and libraries for building cloud-native applications. Alternatives like Spring Cloud, Micronaut, Quarkus, and Helidon are listed as they offer similar context propagation and microservices support features. |
| 70 | qubership-core-control-plane | qubership-core cloud-core, core, go, service-mesh |
✅ | App Definition and Development | Application Definition & Image Build | Helm, Kustomize, Jsonnet | The provided content mentions 'qubership-repo-template', which appears to be a template for creating a repository. Given the context, it seems to be related to defining or managing Kubernetes applications, possibly through templating. This aligns with the 'App Definition and Development' category in the CNCF landscape, specifically under 'Application Definition & Image Build'. Alternatives like Helm, Kustomize, and Jsonnet are also tools used for managing Kubernetes application definitions and templating. |
| 71 | qubership-core-core-operator | qubership-core cloud-core, core, java, quarkus |
❌ | ⛅ | ⛅ | ⛅ | |
| 72 | qubership-core-dbaas-agent | qubership-core cloud-core, core, go |
❌ | ⛅ | ⛅ | ⛅ | |
| 73 | qubership-core-error-handling | qubership-core core, java, lib |
✅ | App Definition and Development | Application Framework | Spring Boot, Micronaut, Quarkus | The provided content describes a Java-based error handling and logging library that integrates with SLF4J and Lombok. It focuses on application-level error management and logging, which aligns with the 'App Definition and Development' category in the CNCF landscape. Specifically, it fits under 'Application Framework' as it provides a structured way to handle errors and logs within applications. Alternatives like Spring Boot, Micronaut, and Quarkus are listed because they also provide comprehensive frameworks for building Java applications, including error handling and logging capabilities. |
| 74 | qubership-core-facade-operator | qubership-core cloud-core, core, go |
❌ | ⛅ | ⛅ | ⛅ | |
| 75 | qubership-core-infra | qubership-core core |
❌ | ⛅ | ⛅ | ⛅ | |
| 76 | qubership-core-ingress-gateway | qubership-core cloud-core, core, envoy, service-mesh |
✅ | Networking | API Gateway | Kong, Traefik, Contour, Gloo | The provided file describes an Ingress Gateway based on the Envoy proxy, which is a common component in API Gateway solutions. The description mentions dynamic configuration loading from a control plane and different types of gateways (public, private, internal, egress), which aligns with the functionality of API Gateways in the CNCF landscape. The alternatives listed are other well-known API Gateway solutions within the CNCF ecosystem that provide similar features. |
| 77 | qubership-core-junit-k8s-extension | qubership-core core, java, lib |
❌ | ⛅ | ⛅ | ⛅ | |
| 78 | qubership-core-lib-go | qubership-core core, go, lib |
✅ | Observability and Analysis | Logging | Fluentd, Loki, OpenTelemetry | The provided file describes a logging package that supports different log levels, customizable log formats, and runtime log level changes. These features are characteristic of logging solutions within the Observability and Analysis category of the CNCF landscape. Specifically, it fits under the Logging subcategory, which includes tools designed to collect, store, and analyze log data. Alternatives like Fluentd, Loki, and OpenTelemetry are mentioned because they are prominent CNCF projects that also provide logging capabilities, with varying focuses such as log aggregation (Fluentd), log storage and querying (Loki), and comprehensive observability (OpenTelemetry). |
| 79 | qubership-core-lib-go-actuator-common | qubership-core core, go, lib |
✅ | Observability and Analysis | Monitoring | Prometheus, OpenTelemetry, Jaeger | The provided file describes a Go library that includes functionality for health checks, API versioning, configuration properties, monitoring, and tracing. The monitoring and tracing features, in particular, align well with the Observability and Analysis category in the CNCF landscape. The library supports Prometheus metrics and OpenTelemetry tracing, which are key technologies in this space. Alternatives like Prometheus, OpenTelemetry, and Jaeger are mentioned because they provide similar functionalities and are widely adopted in the CNCF ecosystem. |
| 80 | qubership-core-lib-go-bg-kafka | qubership-core core, go, lib |
✅ | Messaging and Streaming | Event Brokers | Apache Kafka, NATS, RabbitMQ, Pulsar | The provided file describes a library that abstracts the consumption of messages from Kafka in Cloud-Core Blue Green scenarios. This indicates that the solution is related to messaging and event streaming, specifically around Kafka. The CNCF landscape categorizes Kafka under 'Messaging and Streaming' with a subcategory of 'Event Brokers'. Alternatives include other popular event brokers like Apache Kafka (which is already mentioned), NATS, RabbitMQ, and Pulsar, which are also part of the CNCF landscape. |
| 81 | qubership-core-lib-go-bg-state-monitor | qubership-core core, go, lib |
✅ | Observability and Analysis | Monitoring | Prometheus, Thanos, OpenTelemetry | The provided content describes a Go library for monitoring state, which aligns with the 'Observability and Analysis' category in the CNCF landscape, specifically under 'Monitoring'. The library appears to interact with Consul for state management, suggesting it's used for monitoring distributed systems. Alternatives like Prometheus, Thanos, and OpenTelemetry are also monitoring solutions within the CNCF landscape that provide similar functionalities for tracking system states and metrics. |
| 82 | qubership-core-lib-go-dbaas-arangodb-client | qubership-core core, go, lib |
✅ | Database | NewSQL | TiDB, CockroachDB, YugabyteDB | The provided file describes a Go client library for interacting with ArangoDB databases, specifically designed to work with multi-tenancy and service databases. ArangoDB is a multi-model database that supports key-value, document, and graph data models, which falls under the NewSQL category in the CNCF landscape. The alternatives listed are also NewSQL databases that support similar multi-model capabilities and are part of the CNCF ecosystem. |
| 83 | qubership-core-lib-go-dbaas-base-client | qubership-core core, go, lib |
❌ | Database | n/a ❌ | Vitess, TiDB, CockroachDB | The provided file describes a database client implementation for a REST API (DbAAS) that allows acquiring raw database connections and supports different database types like Cassandra, PostgreSQL, and MongoDB. This fits within the Database category of CNCF as it deals with database connectivity and management. Alternatives like Vitess, TiDB, and CockroachDB are listed as they are also database solutions within the CNCF landscape that provide similar functionalities for managing and connecting to databases. |
| 84 | qubership-core-lib-go-dbaas-cassandra-client | qubership-core core, go, lib |
✅ | Database | NewSQL | Cassandra, ScyllaDB, CockroachDB | The provided file describes a Go client library for interacting with Cassandra databases, specifically designed to work with multi-tenancy and service databases. It includes features like connection pooling, session management, and support for SSL/TLS. Given that Cassandra is a prominent NewSQL database and the library is tailored for Cassandra, the most fitting category in the CNCF landscape is 'Database' with the subcategory 'NewSQL'. Alternatives include other NewSQL databases like ScyllaDB (a Cassandra-compatible database) and CockroachDB (a distributed SQL database). |
| 85 | qubership-core-lib-go-dbaas-clickhouse-client | qubership-core core, go, lib |
✅ | Database | SQL Database | Vitess, TiDB, CockroachDB | The provided file describes a Go client library for interacting with ClickHouse databases, specifically designed to work with multi-tenancy and service databases. It provides functionality for creating and managing database connections, executing queries, and handling SSL/TLS connections. Given its focus on database interaction and management, it fits best under the 'Database' category in the CNCF landscape. The 'SQL Database' subcategory is appropriate as ClickHouse is an SQL database. Alternatives like Vitess, TiDB, and CockroachDB are also SQL databases that support similar functionalities and are part of the CNCF landscape. |
| 86 | qubership-core-lib-go-dbaas-mongo-client | qubership-core core, go, lib |
✅ | Database | NewSQL | Vitess, TiDB, CockroachDB | The provided file describes a Go client library for interacting with MongoDB databases, specifically designed to work with multi-tenancy and service databases. It supports features like connection pooling, SSL/TLS, and integration with dbas-aggregator. Given its focus on database interaction and MongoDB, it best fits under the 'Database' category in the CNCF landscape. The 'NewSQL' subcategory is chosen because MongoDB is a document-oriented database that bridges traditional SQL and NoSQL databases, and the library provides advanced features like multi-tenancy and connection management. Alternatives like Vitess, TiDB, and CockroachDB are also NewSQL databases that offer similar scalability and flexibility. |
| 87 | qubership-core-lib-go-dbaas-opensearch-client | qubership-core core, go, lib |
✅ | Database | Search Engine | Elasticsearch, Apache Solr, OpenSearch | The provided file describes a Go client library for interacting with OpenSearch databases, specifically designed to work with multi-tenancy and service databases. It provides functionality to create, manage, and query OpenSearch indices, aliases, and templates. The solution fits into the 'Database' category of the CNCF landscape, specifically under the 'Search Engine' subcategory, as it is a client library for OpenSearch, which is a search engine. Alternatives like Elasticsearch, Apache Solr, and OpenSearch are listed as they are similar search engine solutions within the CNCF ecosystem. |
| 88 | qubership-core-lib-go-dbaas-postgres-client | qubership-core core, go, lib |
✅ | Database | SQL Database | Vitess, TiDB, CockroachDB | The provided file describes a PostgreSQL client library that facilitates interaction with PostgreSQL databases, particularly in a multi-tenant environment. It supports both service and tenant databases, and it is built on top of the 'uptrace/bun' ORM library and 'pgx' driver. This aligns well with the CNCF's Database category, specifically SQL Database subcategory, as it provides tools for managing and interacting with SQL databases in a cloud-native environment. Alternatives like Vitess, TiDB, and CockroachDB are also SQL databases that offer similar functionalities and are part of the CNCF landscape. |
| 89 | qubership-core-lib-go-error-handling | qubership-core core, go, lib |
✅ | App Definition and Development | Error Handling and Logging | Sentry, OpenTelemetry, Fluentd, Elasticsearch, Prometheus | The provided file describes a Go library for handling exceptions with error codes, which includes features like unique error IDs, error codes in a specific format, error wrapping, stack trace preservation, and integration with logging and HTTP servers (like fiber). This fits well within the 'App Definition and Development' category of the CNCF landscape, specifically under 'Error Handling and Logging' as it provides tools for managing and logging errors in cloud-native applications. Alternatives like Sentry, OpenTelemetry, Fluentd, Elasticsearch, and Prometheus are also focused on monitoring, logging, and error handling in cloud-native environments. |
| 90 | qubership-core-lib-go-fiber-server-utils | qubership-core core, go, lib |
✅ | App Definition and Development | Microservice Tools | Go Micro, Kratos, Go Kit | The provided file describes a Go library (fiber-server-utils) that enhances the Fiber web framework with cloud-native capabilities such as health checks, metrics, tracing, and logging. This fits well under the 'App Definition and Development' category in the CNCF landscape, specifically under 'Microservice Tools', as it provides utilities for building and managing microservices. Alternatives like Go Micro, Kratos, and Go Kit are also listed under similar categories in the CNCF landscape as they provide frameworks and tools for building microservices in Go. |
| 91 | qubership-core-lib-go-maas-bg-segmentio | qubership-core core, go, lib |
✅ | Messaging and Eventing | Message Brokers | Apache Kafka, NATS, RabbitMQ | The provided file describes a library that adapts Blue Green Consumer for a Kafka client, specifically for the Segmentio Kafka Go client. This indicates that the solution is related to messaging systems, particularly Kafka, which is a prominent message broker. The CNCF landscape includes several message brokers, and the described solution fits best within the 'Messaging and Eventing' category, specifically under 'Message Brokers'. Alternatives like Apache Kafka, NATS, and RabbitMQ are also part of this category and are commonly used for similar purposes. |
| 92 | qubership-core-lib-go-maas-client | qubership-core core, go, lib |
✅ | Messaging and Streaming | Message Brokers | Apache Kafka, RabbitMQ, NATS, Pulsar | The provided file describes a Go client for performing operations with Maas, specifically focusing on Kafka and RabbitMQ integrations. The client supports operations such as creating, reading, and deleting topics, as well as message consumption in Blue-Green scenarios. Given the focus on message brokers and streaming, the solution best fits under the 'Messaging and Streaming' category of the CNCF landscape, with 'Message Brokers' as the subcategory. Alternatives like Apache Kafka, RabbitMQ, NATS, and Pulsar are listed as they are prominent CNCF projects in the same space. |
| 93 | qubership-core-lib-go-maas-core | qubership-core core, go, lib |
✅ | App Definition and Development | Application Definition & Image Build | Dapr, Knative, Helm | The provided file describes a library (core-lib-go-maas-core) that provides methods to build MAAS (Metal as a Service) clients with default parameters like logger, namespace, MAAS agent URL, and auth supplier. This fits into the 'App Definition and Development' category as it is a development tool for building applications. The subcategory 'Application Definition & Image Build' is chosen because the library seems to assist in defining and building application components, particularly for MAAS clients. Alternatives like Dapr, Knative, and Helm are listed as they also provide tools and frameworks for building and defining applications in a cloud-native environment. However, the exact functionality of the library is not fully detailed, so the categorization is based on the available information. |
| 94 | qubership-core-lib-go-maas-segmentio | qubership-core core, go, lib |
✅ | Messaging and Eventing | Publish & Subscribe | Apache Kafka, NATS, RabbitMQ, Pulsar | The provided solution is a library that facilitates interaction with Kafka (specifically Kafka-go) for message production and consumption based on topic information received from Maas. It provides methods to create Kafka writers and readers, which are core functionalities in the messaging and eventing domain, specifically under the publish & subscribe model. The library abstracts the underlying Kafka communication details, making it easier to integrate Kafka into applications. Given its focus on Kafka, it naturally fits into the 'Messaging and Eventing' category with 'Publish & Subscribe' as the subcategory. Alternatives like Apache Kafka (the native solution), NATS, RabbitMQ, and Pulsar are also part of the CNCF landscape and serve similar purposes. |
| 95 | qubership-core-lib-go-paas-mediation-client | qubership-core core, go, lib |
❌ | ⛅ | ⛅ | ⛅ | |
| 96 | qubership-core-lib-go-rest-utils | qubership-core core, go, lib |
✅ | Service Mesh | API Gateway | Istio, Linkerd, Envoy, Kong | The described solution is a library for route registration in a control plane, which allows microservices to make REST calls without knowing the URL host. It supports different types of routes (internal, private, public, and facade gateways) and integrates with OpenShift. This functionality aligns with API Gateway and Service Mesh components in the CNCF landscape, which manage traffic routing, load balancing, and service discovery. Alternatives like Istio, Linkerd, Envoy, and Kong provide similar capabilities in managing and routing traffic between services. |
| 97 | qubership-core-lib-go-stomp-websocket | qubership-core core, go, lib |
✅ | Networking | Messaging | NATS, RabbitMQ, Apache Kafka | The provided content describes a Go library for STOMP (Simple Text Oriented Messaging Protocol) over WebSocket, which is primarily used for messaging. This fits well under the 'Networking' category in the CNCF landscape, specifically under the 'Messaging' subcategory. Alternatives like NATS, RabbitMQ, and Apache Kafka are also messaging solutions within the CNCF landscape that provide similar functionality. |
| 98 | qubership-core-maas-agent | qubership-core cloud-core, core, go |
✅ | Security | Identity and Access Management | Keycloak, SPIFFE, Dex | The `maas-agent` described in the file appears to be a proxy for transforming internal M2M security with local IdP to credentials compatible with a global MaaS service. This functionality aligns with Identity and Access Management (IAM) solutions in the CNCF landscape, which handle authentication, authorization, and credential management. Alternatives like Keycloak, SPIFFE, and Dex are also focused on secure identity management and credential handling in cloud-native environments. The description emphasizes security and credential transformation, which is why the 'Security' category and 'Identity and Access Management' subcategory were chosen. |
| 99 | qubership-core-microservice-dependencies | qubership-core core, java, lib |
✅ | App Definition and Development | Microservice Frameworks | Spring Cloud, Micronaut, Quarkus | The provided file describes `cloud-core-java-bom` as a BOM (Bill of Materials) that aggregates cloud-core libraries, excluding the `microservice-framework` library. This suggests it is related to dependency management and microservice development in Java, which aligns with the 'App Definition and Development' category and 'Microservice Frameworks' subcategory in the CNCF landscape. Alternatives like Spring Cloud, Micronaut, and Quarkus are also Java-based frameworks commonly used for building microservices and managing dependencies in cloud-native applications. |
| 100 | qubership-core-microservice-framework | qubership-core core, java, lib |
✅ | Microservices | Microservice Frameworks | Spring Cloud, Micronaut, Quarkus | The provided file describes a microservice framework intended for use in a blocking mode with WebClient, which suggests it is a tool for building microservices. The mention of Spring context initialization and MicroserviceApplicationBuilder further indicates it is a framework for microservices development. Alternatives like Spring Cloud, Micronaut, and Quarkus are also microservice frameworks within the CNCF landscape that provide similar functionality for building and managing microservices. |
| 101 | qubership-core-microservice-framework-extensions | qubership-core core, java, lib |
✅ | App Definition and Development | API Gateway | Spring Cloud Gateway, Kong, Envoy | The provided file describes a framework extension for SpringDoc Swagger that adds additional functionality to handle secured requests (m2m, user, bearer) through Swagger UI. This fits well within the 'App Definition and Development' category as it pertains to API documentation and security, which are key aspects of API gateways. Alternatives like Spring Cloud Gateway, Kong, and Envoy are listed as they also handle API routing, security, and documentation, albeit in different contexts and with varying feature sets. |
| 102 | qubership-core-mongo-evolution | qubership-core core, java, lib |
✅ | Database | Database Migration and Tooling | Liquibase, Flyway, SchemaHero | The provided file describes a library called 'spring-mongo-evolution' which is a wrapper around Java Mongo Evolution. It allows using MongoTemplate in Mongo evolution scripts, which is particularly convenient for Spring Framework users. This library is focused on database schema evolution and migration, specifically for MongoDB. It fits under the 'Database' category in the CNCF landscape, more specifically under 'Database Migration and Tooling' as it provides tools for managing database schema changes. Alternatives like Liquibase, Flyway, and SchemaHero are also tools designed for database schema migration and evolution, making them suitable alternatives. |
| 103 | qubership-core-paas-mediation | qubership-core cloud-core, core, go |
❌ | ⛅ | ⛅ | ⛅ | |
| 104 | qubership-core-process-orchestrator | qubership-core core, java, lib |
✅ | App Definition and Development | Workflow and Orchestration | Argo Workflows, Tekton, Cadence | The provided description outlines a Java-based process orchestration framework that handles task scheduling, execution management, and process flow control. This aligns with the 'Workflow and Orchestration' subcategory under 'App Definition and Development' in the CNCF landscape. Similar solutions in this space include Argo Workflows, Tekton, and Cadence, which also provide workflow and orchestration capabilities for managing complex task dependencies, state management, and error handling. |
| 105 | qubership-core-quarkus-extensions | qubership-core core, java, lib |
✅ | App Definition and Development | Streaming & Messaging | Eclipse Vert.x, Spring Cloud Stream, Apache Kafka | The provided file describes an extension for the Quarkus framework that enables running a STOMP server over WebSockets or standard WebSocket protocol. This functionality falls under the 'Streaming & Messaging' subcategory of the 'App Definition and Development' category in the CNCF landscape. The solution is focused on real-time messaging and communication, which aligns with the purpose of other CNCF projects like Eclipse Vert.x, Spring Cloud Stream, and Apache Kafka, which also provide capabilities for building real-time, event-driven applications. The STOMP protocol is specifically designed for messaging, making this a good fit for the 'Streaming & Messaging' subcategory. |
| 106 | qubership-core-rest-libraries | qubership-core core, java, lib |
✅ | App Definition and Development | Web Frameworks | Spring Cloud Gateway, Envoy, Linkerd | The provided file describes a web client module that facilitates secure requests, automatically inserting JWT tokens, and integrates with Spring Framework. It is primarily a client-side component for making HTTP requests, which aligns with the 'App Definition and Development' category in the CNCF landscape. The 'Web Frameworks' subcategory is chosen because the solution is a framework for building web clients. Alternatives like Spring Cloud Gateway, Envoy, and Linkerd are listed as they provide similar functionalities for handling HTTP requests and API gateways in cloud-native environments. |
| 107 | qubership-core-restclient | qubership-core core, java, lib |
✅ | App Definition and Development | Microservices | Spring Cloud, Micronaut, Quarkus | The provided file describes a microservice implementation based on a REST client (resttemplate or webclient), which falls under the 'App Definition and Development' category in the CNCF landscape. The 'Microservices' subcategory is chosen because the solution is explicitly mentioned as a microservice implementation. Alternatives like Spring Cloud, Micronaut, and Quarkus are listed as they are popular frameworks for building microservices in the Java ecosystem, similar to the described solution. |
| 108 | qubership-core-site-management | qubership-core cloud-core, core, go |
❌ | ⛅ | ⛅ | ⛅ | |
| 109 | qubership-core-springboot-starter | qubership-core core, java, lib |
✅ | App Definition and Development | Microservices Framework | Spring Cloud, Micronaut, Helidon | The provided file describes a Spring Boot starter parent wrapper that brings essential cloud-core libraries and is used for quickly creating microservices using a microservice-framework client. This aligns with the 'App Definition and Development' category in the CNCF landscape, specifically under 'Microservices Framework'. Alternatives like Spring Cloud, Micronaut, and Helidon are also microservice frameworks that provide similar functionality for building cloud-native applications. |
| 110 | qubership-core-utils | qubership-core core, java, lib |
✅ | Security and Compliance | TLS/SSL Libraries | Let's Encrypt, Cert-Manager, OpenSSL, BoringSSL | The provided file describes a lightweight Java library focused on TLS configuration and authentication utilities, which falls under the Security and Compliance category in the CNCF landscape. The library provides features like default TLS configuration with PKIX trust manager, customizable TLS configurations via SPI, SSL context and trust/key store management, and machine-to-machine (M2M) authentication support. These functionalities are typical of security libraries that handle secure communications. Alternatives like Let's Encrypt, Cert-Manager, OpenSSL, and BoringSSL are also focused on TLS/SSL and secure communication, making them suitable alternatives. |
| 111 | qubership-cql-driver | qubership-infra |
❌ | n/a ❌ | n/a ❌ | The provided base64 content decodes to '# qubershiq-cql-driver', which is insufficient to determine the exact nature of the solution or its alignment with any specific CNCF category. More context or a detailed description is needed to accurately categorize the solution and identify suitable alternatives from the CNCF landscape. | |
| 112 | qubership-credential-manager | qubership-infra |
✅ | Security and Compliance | Secrets Management | Vault, Sealed Secrets, External Secrets | The described solution, 'quberSHIP-credential-manager', is focused on managing credentials and secrets in a Kubernetes environment. It provides functionality for handling secrets changes, watching secrets, and updating credentials, which aligns with the 'Secrets Management' subcategory under 'Security and Compliance' in the CNCF landscape. Alternatives like Vault, Sealed Secrets, and External Secrets are also focused on managing secrets in cloud-native environments, making them suitable alternatives. |
| 113 | qubership-dbaas | qubership-core core, dbaas, java |
✅ | Database | Database Proxy and Aggregation | Vitess, ProxySQL, TiDB | The provided description indicates that DBaaS is an aggregator for database adapters, managing requests for administered databases and sending them to the necessary adapter. It stores information about all databases used in a cloud project, isolated by namespace, and uses a Classifier to identify databases within a cloud namespace. This functionality aligns with database proxy and aggregation solutions in the CNCF landscape, such as Vitess, ProxySQL, and TiDB, which also manage database connections, provide aggregation layers, and support multi-tenancy. |
| 114 | qubership-dbaas-adapter-core | qubership-core |
❌ | Database | n/a ❌ | Vitess, TiKV, CloudNativePG | The description mentions 'Kubership DBaaS Adapter Core' as a base library for all Kubership DBaaS adapters, which suggests it is related to database management in a cloud-native environment. Given the focus on databases and adapters, the most fitting CNCF category is 'Database'. Alternatives like Vitess, TiKV, and CloudNativePG are also cloud-native database solutions or tools that facilitate database operations in Kubernetes environments. |
| 115 | qubership-dbaas-client | qubership-core core, dbaas, java, lib |
✅ | Database | Database Clients and Libraries | HikariCP, Agroal, Vitess | The provided file describes a Java DBaaS (Database as a Service) client library that provides utility methods for tests, specifically for working with a database pool and cache. This fits well under the 'Database' category in the CNCF landscape, specifically under 'Database Clients and Libraries'. Alternatives like HikariCP, Agroal, and Vitess are also database connection pooling and management tools that are part of the CNCF ecosystem. |
| 116 | qubership-deployment-status-provisioner | qubership-infra saqs |
❌ | ⛅ | ⛅ | ⛅ | |
| 117 | qubership-diag-proxy | qubership-ossf-request observability, proxy |
✅ | Observability and Analysis | Tracing | Jaeger, Zipkin, OpenTelemetry | The described solution, 'diag-proxy', is a proxy based on Nginx that facilitates the collection and forwarding of diagnostic information (profiling and tracing data) to respective collectors in different namespaces. It simplifies the configuration of addresses for profiling agents (like Profiler) and tracing agents (like Jaeger, Zipkin, or OpenTelemetry). This functionality aligns with the CNCF category of 'Observability and Analysis', specifically under 'Tracing', as it deals with the collection and management of trace data. Alternatives like Jaeger, Zipkin, and OpenTelemetry are listed as they are prominent CNCF projects that handle tracing data collection and analysis, similar to what 'diag-proxy' aims to facilitate. |
| 118 | qubership-disaster-recovery-daemon | qubership-infra k8sstream |
✅ | Orchestration & Management | Disaster Recovery | Velero, Kasten, OpenEBS | The 'Qubership Disaster Recovery Daemon' (DRD) is a service that establishes communication between the Site Manager and the current cluster operator or disaster recovery controller. It provides features like managing disaster recovery resources and implementing DR controllers for services without an operator. This aligns with the CNCF category of 'Orchestration & Management' under 'Disaster Recovery' as it focuses on managing and recovering Kubernetes resources during disasters. Alternatives like Velero, Kasten, and OpenEBS are also part of the CNCF landscape and provide similar disaster recovery capabilities for Kubernetes environments. |
| 119 | qubership-docker-integration-tests | qubership-infra saqs |
❌ | Testing | n/a ❌ | Sonobuoy, Testkube | The provided description mentions a 'Robot Framework library' that provides basic keywords to write RF integration tests for Kubernetes-based applications. This suggests the solution is focused on testing within a Kubernetes environment. The CNCF landscape includes testing tools like Sonobuoy (for conformance testing) and Testkube (for running tests in Kubernetes), which are similar in purpose. The category 'Testing' is chosen as it best fits the described functionality of the solution. |
| 120 | qubership-docker-opensearch | qubership-infra opensearch, saqs |
✅ | Security and Compliance | Policy Management | Open Policy Agent (OPA), Kyverno, Falco | The provided file describes a security filtering plugin for OpenSearch that manages access control and policy enforcement for Index State Management (ISM) operations. This functionality aligns with the 'Security and Compliance' category in the CNCF landscape, specifically under 'Policy Management'. The plugin checks user permissions and enforces policies for various ISM actions, which is similar to what solutions like Open Policy Agent (OPA), Kyverno, and Falco offer in the CNCF ecosystem. These alternatives also provide policy enforcement and security filtering capabilities, making them suitable comparisons. |
| 121 | qubership-env-checker | qubership-ossf-request observability |
✅ | App Definition and Development | Testing | Sonobuoy, kube-bench, Polaris | The described solution, 'qubership-env-checker', is an independent microservice designed to validate Kubernetes or OpenShift environments. It performs checks on infrastructure, Kubernetes entities, labels, annotations, variables, and generates detailed reports. This functionality aligns with the 'Testing' subcategory under 'App Definition and Development' in the CNCF landscape, as it focuses on validating and ensuring the correctness of cloud-native environments. Alternatives like Sonobuoy, kube-bench, and Polaris are also tools in the CNCF landscape that perform similar validation and compliance checks for Kubernetes environments. |
| 122 | qubership-envgene | qubership-devops |
✅ | App Definition and Development | Application Configuration | Kustomize, Helm, Jsonnet | The provided file describes a tool named 'EnvGene' which is used for environment generation and configuration management. It involves defining environments, templates, and configurations in YAML files, which aligns with the 'Application Configuration' subcategory under 'App Definition and Development' in the CNCF landscape. Similar tools in this space include Kustomize, Helm, and Jsonnet, which are also used for managing and templating application configurations. |
| 123 | qubership-envgene-instance | qubership-devops |
❌ | n/a ❌ | n/a ❌ | The provided base64-encoded content decodes to '# qubership-envgen-instance', which is insufficient to determine the category or subcategory within the CNCF landscape. No meaningful description or context is provided to analyze the solution's purpose, functionality, or components. Therefore, no accurate classification or alternatives can be suggested. | |
| 124 | qubership-envgene-template | qubership-devops |
❌ | n/a ❌ | n/a ❌ | n/a ❌ | The provided file content is a base64-encoded string 'IyBxdWJlcnNoaXAtZW52Z2VuZS10ZW1wbGF0ZQ==', which decodes to '# qubership-envgen-engine-template'. This is insufficient to determine the category or subcategory within the CNCF landscape, as it lacks descriptive details about the solution's functionality or purpose. No meaningful alternatives can be suggested without further context. |
| 125 | qubership-external-logging-installer | qubership-ossf-request logging, observability |
✅ | Observability and Analysis | Logging | Fluent Bit, Promtail, OpenTelemetry Collector | The provided file describes FluentD as a tool for collecting self logs from containers on a VM and sending them to Graylog. This functionality falls under the 'Logging' subcategory of 'Observability and Analysis' in the CNCF landscape. FluentD is a well-known log collector and processor, and alternatives like Fluent Bit (a lighter-weight version of FluentD), Promtail (part of the Grafana Loki stack), and OpenTelemetry Collector (which can also handle logs) are similar solutions within the CNCF ecosystem. |
| 126 | qubership-fluent-pipeline-tests | qubership-ossf-request logging, observability, testing |
✅ | Observability and Analysis | Logging | Fluentd, Fluent Bit, Logstash, Vector | The provided content discusses a testing pipeline for Fluentd and Fluent Bit, which are well-known logging agents in the CNCF landscape. The mention of 'fluentd', 'fluentbit', and 'fluentbit-ha' suggests that the solution is related to log collection and processing. Fluentd and Fluent Bit are both part of the CNCF logging subcategory, and alternatives like Logstash and Vector also fit into this category as they serve similar purposes in log management and processing. |
| 127 | qubership-fluentd | qubership-ossf-request logging, observability |
✅ | Observability and Analysis | Logging | Fluent Bit, Logstash, Vector | The provided file describes a custom FluentD image with additional plugins installed. FluentD is a widely used log collector and processor, which falls under the 'Logging' subcategory of 'Observability and Analysis' in the CNCF landscape. Alternatives like Fluent Bit (a lighter version of FluentD), Logstash, and Vector are also popular logging solutions within the CNCF ecosystem. |
| 128 | qubership-git-system-follower | qubership-devops |
✅ | App Definition and Development | Package Management | Helm, Kustomize, Flux, Argo CD | The solution described in the file is a package manager for Git providers, specifically designed to manage repository branch content and configuration. It automates installations, updates, and removals, ensuring consistency and reducing manual intervention. This aligns with the 'Package Management' subcategory under 'App Definition and Development' in the CNCF landscape. Alternatives like Helm, Kustomize, Flux, and Argo CD are also tools that manage configurations and packages in a cloud-native environment, though they may focus more on Kubernetes-specific scenarios. |
| 129 | qubership-grafana-plugins-init | qubership-ossf-request monitoring, observability |
✅ | Observability and Analysis | Monitoring | Prometheus, Thanos, Cortex | The provided file describes a container for Grafana customization with predefined plugins. Grafana is a popular open-source platform for monitoring and observability, which aligns with the 'Observability and Analysis' category in the CNCF landscape. Specifically, it falls under 'Monitoring' as it is used to visualize and analyze metrics. Alternatives like Prometheus, Thanos, and Cortex are also part of the CNCF landscape and serve similar purposes in monitoring and observability. |
| 130 | qubership-grafana-reporter | qubership-ossf-request monitoring, observability |
✅ | Monitoring | Dashboards | Grafana, Prometheus, Thanos, VictoriaMetrics | The solution described is a Grafana reporter, which generates dashboard reports in PDF format. It integrates with Grafana to fetch dashboard data and render panels. This fits into the Monitoring category under Dashboards, as it is specifically designed to work with Grafana dashboards. Alternatives include other monitoring and dashboard solutions that are part of the CNCF landscape, such as Grafana itself, Prometheus, Thanos, and VictoriaMetrics, which are commonly used for monitoring and visualization in cloud-native environments. |
| 131 | qubership-graphite-remote-adapter | qubership-ossf-request monitoring, observability |
❌ | Monitoring | n/a ❌ | Prometheus, Grafana, Thanos | The provided file describes a package named 'ui' that contains static files and templates used in the web UI, which are compiled into the Prometheus Remote Adapter binary using the go-bindata tool. This suggests that the solution is related to monitoring, specifically in the context of Prometheus, which is a well-known project under the CNCF. The alternatives listed are other monitoring solutions within the CNCF landscape that are commonly used alongside or as alternatives to Prometheus. |
| 132 | qubership-graylog-archiving-plugin | qubership-ossf-request logging, observability, plugin |
✅ | Storage | Backup & Restore | Velero, Stash, Kasten K10 | The Graylog Archiving Plugin is designed for archiving Elasticsearch indices, which falls under the category of backup and restore solutions in the CNCF landscape. It provides functionality to create, manage, and restore archives of Elasticsearch indices, similar to other backup and restore tools like Velero, Stash, and Kasten K10. The plugin supports both file-system and S3 storage for archives, making it a versatile solution for data backup in cloud-native environments. |
| 133 | qubership-graylog-auth-proxy | qubership-ossf-request logging, observability, proxy |
✅ | Security and Compliance | Authentication and Authorization | Dex, Keycloak, OAuth2 Proxy | The solution described is a proxy that handles authentication and authorization for users accessing the Graylog server using third-party databases like LDAP or OAuth services (e.g., Keycloak). It fits under the 'Security and Compliance' category because it deals with securing access to applications via authentication mechanisms. The 'Authentication and Authorization' subcategory is appropriate as it specifically handles user authentication and role/permission mapping. Alternatives like Dex, Keycloak, and OAuth2 Proxy are listed because they provide similar functionality in managing authentication and authorization in cloud-native environments. |
| 134 | qubership-graylog-obfuscation-plugin | qubership-ossf-request logging, observability, plugin |
✅ | Security | Policy & Governance | Open Policy Agent (OPA), Falco, Kyverno | The provided file describes a plugin for automatic analysis and obfuscation of input log messages, which aligns with security and policy enforcement tools in the CNCF landscape. The plugin seems to focus on log obfuscation, which is a security feature to protect sensitive data. Alternatives like Open Policy Agent (OPA), Falco, and Kyverno are also focused on security and policy enforcement, making them suitable comparisons. The mention of SuperLinter suggests integration with CI/CD pipelines, which is common in policy and governance tools. |
| 135 | qubership-graylog-plugins-init | qubership-ossf-request logging, observability |
✅ | Observability and Analysis | Logging | Fluentd, Fluent Bit, Logstash | The provided file describes an init container for customizing Graylog with predefined plugins. Graylog is a centralized logging solution that falls under the 'Observability and Analysis' category in the CNCF landscape, specifically under the 'Logging' subcategory. The described solution involves downloading and managing plugins for Graylog, which is similar to how other logging solutions like Fluentd, Fluent Bit, and Logstash operate. These alternatives are also part of the CNCF landscape and serve similar purposes in log management and processing. |
| 136 | qubership-hive-metastore | qubership-infra |
✅ | Database | Data Warehouse | Apache Hive, Presto, Trino | The solution described is focused on deploying Hive-Metastore in Kubernetes, which is a metadata storage service for Hive, a data warehouse software. Hive-Metastore is a critical component for managing metadata in data warehousing solutions. The alternatives listed (Apache Hive, Presto, Trino) are also data warehousing solutions that can interact with Hive-Metastore. The mention of Trino and Spark in the documentation further supports the categorization under Data Warehouse, as these tools are commonly used for querying and processing large datasets in a data warehouse context. |
| 137 | qubership-hub-test | qubership-devops |
❌ | ⛅ | ⛅ | ⛅ | |
| 138 | qubership-integration-catalog-library | qubership-integration broadcast-pilot, qip |
✅ | App Definition and Development | Application Definition & Image Build | Backstage, Tilt, Shipa | The description mentions that 'Catalog Library' is part of a global integration solution and involves building a proper code transition between 'Runtime Catalog' and 'Design Time Catalog' microservices. This suggests it is related to application development and management, specifically in the context of microservices and integration. The CNCF category 'App Definition and Development' fits well here, with 'Application Definition & Image Build' as a subcategory. Alternatives like Backstage, Tilt, and Shipa are also focused on developer tools and application management, making them suitable comparisons. |
| 139 | qubership-integration-checkstyle | qubership-integration qip |
❌ | App Definition and Development | Application Definition & Image Build | n/a ❌ | The provided content describes a configuration for an integration solution called 'qubership-integration-platform'. However, the description is too vague to definitively categorize it within the CNCF landscape. Based on the mention of 'configuration' and 'integration solution', it might fall under 'App Definition and Development' as it could relate to defining or building applications. However, without more details about the functionality or purpose of the solution, it's impossible to accurately categorize or suggest alternatives. The GitHub link provided does not offer additional context without further investigation. |
| 140 | qubership-integration-designtime-catalog | qubership-integration broadcast-pilot, qip |
✅ | App Definition and Development | Microservices Tools | Istio, Linkerd, Consul | The provided description mentions a microservice handling design time configuration, which is part of a global integration solution. This fits well within the 'App Definition and Development' category, specifically under 'Microservices Tools', as it deals with configuration and integration of microservices. Alternatives like Istio, Linkerd, and Consul are listed as they are prominent tools in the CNCF landscape for managing microservices configurations and integrations. |
| 141 | qubership-integration-engine | qubership-integration broadcast-pilot, qip |
✅ | Integration & Delivery | Service Integration | Apache Camel, Kubernetes Service Mesh (Istio, Linkerd), Cloud Native Buildpacks | The solution described in the file appears to be a part of a global integration platform, specifically handling configuration and runtime orchestration via Apache Camel logic and specifications. It is closely related to service integration and delivery, which fits under the 'Integration & Delivery' category in the CNCF landscape. The mention of Docker and microservices further supports this categorization. Alternatives like Apache Camel and Kubernetes Service Mesh (Istio, Linkerd) are listed as they are prominent tools in the CNCF landscape for service integration and orchestration. The use of Docker also suggests Cloud Native Buildpacks as an alternative for building and deploying containerized applications. |
| 142 | qubership-integration-platform | qubership-integration broadcast-pilot, qip |
✅ | App Definition and Development | Package Management | Helm, Kustomize, Operator Framework | The provided file contains a series of commands related to managing Kubernetes applications using Helm, which is a package manager for Kubernetes. Helm is used for deploying, upgrading, and managing applications on Kubernetes clusters. The file includes commands for installing, upgrading, rolling back, and uninstalling Helm charts, as well as interacting with Kubernetes resources using kubectl. Given this context, the solution best fits under the 'App Definition and Development' category and the 'Package Management' subcategory in the CNCF landscape. Alternatives like Kustomize and Operator Framework are also tools in the same space, providing similar functionalities for managing Kubernetes applications. |
| 143 | qubership-integration-runtime-catalog | qubership-integration broadcast-pilot, qip |
✅ | App Definition and Development | Application Definition & Image Build | Helm, Kustomize, Operator Framework | The provided content describes Runtime Catalog as part of a global integration solution, which handles runtime configuration and is utilized by a microservice (Engine). This suggests it is involved in managing application configurations and deployments, aligning with the 'App Definition and Development' category. Subcategory 'Application Definition & Image Build' fits as it involves tools for defining and building applications. Alternatives like Helm, Kustomize, and Operator Framework are similar in managing application configurations and deployments in cloud-native environments. |
| 144 | qubership-integration-schemas | qubership-integration qip |
❌ | ⛅ | ⛅ | ⛅ | |
| 145 | qubership-integration-sessions-management | qubership-integration broadcast-pilot, qip |
✅ | App Definition and Development | Microservices Management | Istio, Linkerd, Consul | The provided description mentions a microservice that manages sessions created during the execution of integration flows called 'chains' and stores these sessions in OpenSearch. This functionality aligns with microservices management, which is a part of the 'App Definition and Development' category in the CNCF landscape. Alternatives like Istio, Linkerd, and Consul are also involved in managing microservices and their communications, making them relevant comparisons. |
| 146 | qubership-integration-ui | qubership-integration qip |
❌ | n/a ❌ | n/a ❌ | n/a ❌ | The provided base64 content decodes to 'qubership-integration-ui', which is insufficient to determine the exact category or subcategory within the CNCF landscape. More context or a detailed description of the solution's functionality, architecture, and use cases is needed to accurately classify it and identify suitable alternatives. |
| 147 | qubership-integration-variables-management | qubership-integration broadcast-pilot, qip |
✅ | App Definition and Development | Application Definition & Image Build | Helm, Kustomize, Jsonnet | The provided content describes a solution for managing variables within integration flows, which is a part of application configuration and definition. The solution is mentioned to be part of a global integration platform and is installed via Docker Compose, indicating it is likely used in the context of cloud-native application development. Alternatives like Helm, Kustomize, and Jsonnet are tools within the CNCF landscape that also handle configuration management and templating for cloud-native applications. The description suggests a focus on variables management within microservices, which aligns with the 'App Definition and Development' category, specifically under 'Application Definition & Image Build' where configuration management tools are typically classified. |
| 148 | qubership-inventory-tool-cli | qubership-ossf-request observability |
✅ | App Definition and Development | Application Definition & Image Build | Helm, Kustomize, Skaffold | The provided file describes a Java application build and packaging process using Maven, along with instructions for running and configuring the application. This fits well into the 'App Definition and Development' category of the CNCF landscape, specifically under 'Application Definition & Image Build' as it involves defining and building the application. Alternatives like Helm, Kustomize, and Skaffold are tools that also help in defining, building, and managing applications, though they are more Kubernetes-centric. The file does not provide enough information to determine if the solution is specifically for cloud-native environments, but the build and run instructions suggest it is more related to application development and packaging. |
| 149 | qubership-inventory-tool-core | qubership-ossf-request observability |
✅ | App Definition and Development | Application Definition & Image Build | Helm, Kustomize, Operator Framework | The provided base64 content decodes to '# Qubership inventory-tool-core library', which suggests it might be a tool or library related to Kubernetes (given the mention of 'Qubership', possibly a play on 'Kubernetes'). The description is minimal, but it hints at an inventory tool, which could be related to managing or defining applications or resources within a Kubernetes environment. The category 'App Definition and Development' fits as it involves tools that help define, build, and manage applications in cloud-native environments. Subcategory 'Application Definition & Image Build' is chosen as it includes tools for defining applications and their components. Alternatives like Helm, Kustomize, and Operator Framework are listed as they are popular CNCF tools for managing Kubernetes applications and resources. |
| 150 | qubership-jaeger | qubership-ossf-request broadcast-pilot, observability, tracing |
✅ | Observability and Analysis | Monitoring | Prometheus, OpenMetrics, Thanos | The description indicates that the 'Readiness Probe' is used for executing checks and providing custom readiness probes for Jaeger, which is a part of monitoring and observability in cloud-native environments. The solution fits well within the 'Observability and Analysis' category of the CNCF landscape, specifically under 'Monitoring'. Alternatives like Prometheus, OpenMetrics, and Thanos are listed as they are prominent CNCF projects in the monitoring space that also deal with health checks and system readiness. |
| 151 | qubership-kafka | qubership-infra kafka, saqs |
❌ | ⛅ | ⛅ | ⛅ | |
| 152 | qubership-kube-events-generator | qubership-ossf-request logging, observability, testing |
✅ | App Definition and Development | Application Definition & Image Build | Argo Events, Knative Eventing, NATS Streaming | The provided file describes a Kubernetes event generator, which is a tool for generating Kubernetes events. This falls under the 'App Definition and Development' category in the CNCF landscape, specifically under 'Application Definition & Image Build' as it involves creating and managing events within a Kubernetes environment. Alternatives like Argo Events, Knative Eventing, and NATS Streaming are also tools that handle event generation and management within cloud-native ecosystems. |
| 153 | qubership-kube-events-reader | qubership-ossf-request logging, observability |
✅ | Observability and Analysis | Logging | Fluentd, Fluent Bit, Prometheus, Grafana | The solution described is a Kubernetes events reader that collects and processes Kubernetes events, sending them to configured outputs like logs (to be processed by Fluentd/FluentBit) or metrics (to be scraped by Prometheus). This fits under the 'Observability and Analysis' category in the CNCF landscape, specifically under 'Logging' as it deals with event collection and logging. Alternatives like Fluentd and Fluent Bit are also logging solutions, while Prometheus and Grafana are more focused on metrics, which the solution also supports. |
| 154 | qubership-landscape-config | qubership-landscape |
✅ | App Definition and Development | Configuration | Kustomize, Helm, Jsonnet | The provided file describes a project that extends/overrides the base configuration of the CNCF landscape. It involves managing configuration files in YAML format, merging them into a base configuration, and handling additional items like logos and icons. This fits well under the 'Configuration' subcategory of 'App Definition and Development' in the CNCF landscape. Alternatives like Kustomize, Helm, and Jsonnet are also configuration management tools that help in managing and deploying applications in a cloud-native environment. |
| 155 | qubership-landscape-config-processor | qubership-landscape |
✅ | App Definition and Development | Configuration | kustomize, helm, jsonnet | The solution described is a tool for managing and merging YAML configuration files, specifically for the CNCF Landscape application. This falls under the 'Configuration' subcategory of 'App Definition and Development' in the CNCF landscape. Alternatives like 'kustomize', 'helm', and 'jsonnet' are also configuration management tools that handle YAML files and are part of the CNCF ecosystem. The described tool's functionality is similar to these alternatives, as it focuses on merging and managing YAML configurations for a cloud-native application. |
| 156 | qubership-log-exporter | qubership-ossf-request logging, observability |
✅ | Observability and Analysis | Logging | Fluentd, Logstash, Vector | The described solution, 'log-exporter', is designed to evaluate Prometheus metrics based on logs retrieved from Graylog, New Relic, or Loki via API. It processes logs to generate metrics (counter, gauge, histogram) and exports them to Prometheus or VictoriaMetrics. This functionality aligns with the 'Observability and Analysis' category in the CNCF landscape, specifically under 'Logging' subcategory, as it deals with log processing and metric generation. Alternatives like Fluentd, Logstash, and Vector are also log processing tools that can transform logs into metrics and export them to various backends, making them suitable alternatives. |
| 157 | qubership-log-generator | qubership-ossf-request logging, observability |
✅ | Observability and Analysis | Logging | Fluentd, Loki, Elasticsearch (EFK stack) | The Quberchip Log Generator is a tool designed to generate high load logs for performance testing and debugging purposes. It allows for the creation of logs based on predefined templates (Java, Go, JSON logs) and custom patterns, which aligns with the functionality of logging tools in the CNCF landscape. It provides metrics related to log generation and application performance, similar to other observability tools. The solution fits best under the 'Logging' subcategory of 'Observability and Analysis' in the CNCF landscape. Alternatives like Fluentd, Loki, and Elasticsearch are mentioned as they are prominent logging solutions within the CNCF ecosystem that handle log generation, aggregation, and analysis. |
| 158 | qubership-logging-operator | qubership-ossf-request logging, observability |
❌ | n/a ❌ | n/a ❌ | The provided content does not contain enough information to determine the CNCF category or subcategory. The description mentions Lua scripts for parsing key-value pairs and updating levels, but it does not provide details about the broader solution, framework, or application these scripts are part of. Without additional context about the purpose, architecture, or use case of the overall solution, it is impossible to accurately categorize it within the CNCF landscape or suggest alternatives. | |
| 159 | qubership-maas | qubership-core core, go, maas |
✅ | Messaging and Streaming | Message Brokers | RabbitMQ, Kafka, NATS, Pulsar | The solution described, Maas (Messaging as a Service), is focused on managing messaging entities like queues, exchanges, and topics on RabbitMQ and Kafka brokers. It provides declarative configuration and REST API for managing these entities, which aligns with the messaging and streaming category in the CNCF landscape. The solution also supports Blue/Green deployments and integrates with microservices, which are common use cases in cloud-native messaging systems. Alternatives like RabbitMQ, Kafka, NATS, and Pulsar are also part of the CNCF landscape and serve similar purposes in messaging and streaming. |
| 160 | qubership-maas-client | qubership-core core, java, lib, maas |
✅ | Messaging and Eventing | Message Brokers | RabbitMQ, Apache Kafka, NATS, Apache Pulsar | The provided file describes a module that works with RabbitMQ's blue/green deployment mode, focusing on dynamic queue creation and management during microservice runtime. This fits squarely within the 'Messaging and Eventing' category of the CNCF landscape, specifically under 'Message Brokers'. RabbitMQ is a well-known message broker, and alternatives like Apache Kafka, NATS, and Apache Pulsar are also prominent in this space, offering similar capabilities for dynamic message queuing and event-driven architectures. |
| 161 | qubership-maas-client-quarkus | qubership-core core, java, lib, maas |
✅ | App Definition and Development | Streaming & Messaging | Apache Kafka, RabbitMQ, NATS | The provided file describes a Quarkus extension for a Maas client, which includes support for Kafka and RabbitMQ. This suggests that the solution is related to messaging and streaming, which falls under the 'Streaming & Messaging' subcategory of the 'App Definition and Development' category in the CNCF landscape. Alternatives like Apache Kafka, RabbitMQ, and NATS are also part of this subcategory and provide similar functionalities. |
| 162 | qubership-maas-client-spring | qubership-core core, java, lib, maas |
✅ | App Definition and Development | Message Queue | RabbitMQ, Apache Kafka, NATS | The provided file describes a solution that involves dynamic queue bindings, versioned exchanges, and the use of RabbitMQ (evident from classes like `MaasRabbitLocalDevConfig` and annotations like `@EnableDynamicQueueBindings`). This aligns with the 'Message Queue' subcategory under 'App Definition and Development' in the CNCF landscape. Alternatives like RabbitMQ, Apache Kafka, and NATS are listed as they are prominent message queue solutions in the CNCF ecosystem. |
| 163 | qubership-maas-declarative-client-commons | qubership-core core, java, lib, maas |
✅ | App Definition and Development | Streaming & Messaging | Apache Kafka, NATS, RabbitMQ, Pulsar | The provided file describes a module that provides a common framework to decoratively create Kafka consumers and producers, which falls under the 'Streaming & Messaging' subcategory of the 'App Definition and Development' category in the CNCF landscape. The module is specifically designed to work with Kafka, and the connection properties for topics are received from Maas. Alternatives include other messaging systems like Apache Kafka (which is directly mentioned), NATS, RabbitMQ, and Pulsar, which are also part of the CNCF landscape and serve similar purposes. |
| 164 | qubership-maas-declarative-client-quarkus | qubership-core core, java, lib, maas |
✅ | ERROR CATEGORY | ERROR SUBCATEGORY | ||
| 165 | qubership-maas-declarative-client-spring | qubership-core core, java, lib, maas |
✅ | ERROR CATEGORY | ERROR SUBCATEGORY | ||
| 166 | qubership-mistral | qubership-infra |
✅ | App Definition and Development | Application Definition & Image Build | Tekton, Argo, Cloud Native Buildpacks | The provided content describes a process for creating custom actions within a Python library, specifically for Mistral, which involves setting up a Python package, defining custom actions, and building Docker images to include these actions. This aligns with the 'App Definition and Development' category in the CNCF landscape, particularly under 'Application Definition & Image Build', as it involves defining application components and building container images. Alternatives like Tekton, Argo, and Cloud Native Buildpacks are suitable as they provide frameworks for building and defining applications in a cloud-native environment, including CI/CD pipelines and image building. |
| 167 | qubership-mistral-operator | qubership-infra |
✅ | ERROR CATEGORY | ERROR SUBCATEGORY | ||
| 168 | qubership-mongodb-driver | qubership-infra |
❌ | Database | n/a ❌ | MongoDB, PostgreSQL, MySQL, Cassandra, CockroachDB | The file mentions 'mongodb-driver' in the title, which suggests that the solution is related to MongoDB, a popular NoSQL database. The content provides instructions on how to get started, integrate with tools, collaborate with a team, and deploy, which are common activities around database drivers. The alternatives listed are other well-known databases and database drivers within the CNCF landscape that serve similar purposes. |
| 169 | qubership-monitoring-operator | qubership-ossf-request monitoring, observability |
❌ | Monitoring | n/a ❌ | Prometheus, Grafana, Alertmanager, Thanos, VictoriaMetrics | The provided file describes a monitoring solution that includes components like Grafana, Prometheus, Alertmanager, and VictoriaMetrics. These components are used for monitoring and alerting in a cloud-native environment. The file also mentions various exporters and adapters, which are typical in monitoring setups. The CNCF landscape categorizes these components under 'Monitoring'. Alternatives like Prometheus, Grafana, Alertmanager, Thanos, and VictoriaMetrics are also part of the CNCF landscape and serve similar purposes. |
| 170 | qubership-network-latency-exporter | qubership-ossf-request monitoring, observability |
✅ | Observability and Analysis | Monitoring | Prometheus, InfluxDB, OpenTelemetry | The solution described is a network latency exporter that collects RTT and TTL metrics and sends them to InfluxDB or Prometheus. This fits squarely within the Observability and Analysis category of the CNCF landscape, specifically under Monitoring. It is similar to other monitoring tools like Prometheus and InfluxDB, which also collect and store metrics. OpenTelemetry is also listed as an alternative as it provides a framework for collecting metrics, traces, and logs, though it is more general-purpose compared to the described solution. |
| 171 | qubership-nifi | qubership-nifi nifi |
✅ | App Definition and Development | Workflow Orchestration | Apache NiFi, Argo Workflows, Tekton Pipelines | The solution described is a fork of Apache NiFi, which is a dataflow platform designed to automate the movement of data between systems. It fits into the 'Workflow Orchestration' subcategory under 'App Definition and Development' in the CNCF landscape because it focuses on managing and automating data workflows. The additional features like integration with Consul for configuration management and automated configuration restore further emphasize its role in workflow orchestration. Alternatives like Apache NiFi (the original), Argo Workflows, and Tekton Pipelines are also workflow orchestration tools that manage and automate workflows, making them suitable alternatives. |
| 172 | qubership-nifi-registry | qubership-nifi nifi-registry |
✅ | App Definition and Development | Database | Apache NiFi Registry, PostgreSQL | The solution described is a fork of Apache NiFi Registry with additional support for PostgreSQL database storage and configuration. It falls under the 'App Definition and Development' category because it is a tool designed to manage and version control data flows, which is a key aspect of application development. The 'Database' subcategory is chosen due to its enhanced support for PostgreSQL. Alternatives include the original Apache NiFi Registry and PostgreSQL, as they are directly related to the described functionality. |
| 173 | qubership-nosqldb-operator-core | qubership-infra |
✅ | Database | Database Operator | KubeDB, Percona Operator for MySQL, Crunchy PostgreSQL Operator | The provided file name 'qubership-nosqldb-operator-core' suggests that this is a Kubernetes operator for managing NoSQL databases. Operators fall under the 'Database' category in the CNCF landscape, specifically under the 'Database Operator' subcategory. Alternatives like KubeDB, Percona Operator for MySQL, and Crunchy PostgreSQL Operator are also Kubernetes operators that manage databases, making them suitable alternatives. |
| 174 | qubership-observability-examples | qubership-observability examples, observability |
❌ | Observability and Analysis | n/a ❌ | Prometheus, Grafana, Jaeger, Fluentd, OpenTelemetry | The filename 'qubership-observability-examples' suggests that the content is related to observability, which is a key category in the CNCF landscape. Observability tools help in monitoring, logging, and tracing applications. Given the lack of detailed content, the best-fit category is 'Observability and Analysis'. Alternatives include well-known CNCF projects like Prometheus for monitoring, Grafana for visualization, Jaeger for tracing, Fluentd for logging, and OpenTelemetry for a unified observability framework. |
| 175 | qubership-observability-operator | qubership-observability observability |
✅ | Observability and Analysis | Monitoring | Prometheus, Thanos, OpenTelemetry, Grafana | The file name 'qubership-observability-operator' suggests that the solution is related to observability, which is a key category in the CNCF landscape. Given the focus on observability, it likely falls under the 'Observability and Analysis' category with a subcategory of 'Monitoring'. Alternatives like Prometheus, Thanos, OpenTelemetry, and Grafana are well-known CNCF projects in the observability space, which provide similar functionalities for monitoring and observability. |
| 176 | qubership-open-telemetry-collector | qubership-ossf-request observability |
✅ | Observability and Analysis | Tracing | Jaeger, Zipkin, Prometheus, OpenTelemetry | The provided file describes an implementation based on OpenTelemetry Collector, which is a tool for receiving, processing, and exporting telemetry data (traces, metrics, and logs). OpenTelemetry is a part of the CNCF landscape under the 'Observability and Analysis' category, specifically in the 'Tracing' subcategory. The file mentions support for various modules and exporters like Jaeger, Zipkin, and Prometheus, which are also part of the CNCF landscape and serve similar purposes. Therefore, the solution fits best in the 'Observability and Analysis' category with a focus on 'Tracing'. |
| 177 | qubership-opensearch | qubership-infra opensearch, saqs |
❌ | n/a ❌ | n/a ❌ | n/a ❌ | The provided content is insufficient to determine the exact category within the CNCF landscape. It mentions the 'Robot Framework' (http://robotframework.org/), which is a generic test automation framework, but does not provide enough context about its cloud-native usage or integration. Without additional details on how it fits into cloud-native ecosystems (e.g., Kubernetes testing, CI/CD tooling, or observability), a proper classification cannot be made. Alternatives are also unclear due to the lack of context. |
| 178 | qubership-opensearch-curator | qubership-infra opensearch, saqs |
✅ | Management and Governance | Cost Management | kube-janitor, kube-cleanup, kube-downscaler | The Elasticsearch Indices Cleaner is a tool designed to manage and clean up Elasticsearch indices based on predefined patterns, which aligns with the 'Management and Governance' category in the CNCF landscape. Specifically, it falls under 'Cost Management' as it helps in reducing storage costs by deleting old or unnecessary indices. Alternatives like 'kube-janitor', 'kube-cleanup', and 'kube-downscaler' serve similar purposes in managing and cleaning up resources in a Kubernetes environment, though they are not specific to Elasticsearch. |
| 179 | qubership-opensearch-dbaas-adapter | qubership-infra opensearch, saqs |
✅ | Database | Search Indexing | Elasticsearch, OpenSearch, Apache Solr, Meilisearch | The provided file describes a REST API for a DBaaS OpenSearch adapter, which is used to manage databases, users, and resources within an OpenSearch environment. OpenSearch is a search and analytics engine derived from Elasticsearch, and it falls under the Database category in the CNCF landscape, specifically under Search Indexing. The adapter provides functionalities like creating databases, managing users, and handling backups, which are typical for search indexing solutions. Alternatives like Elasticsearch, OpenSearch, Apache Solr, and Meilisearch are mentioned as they are similar search and indexing solutions within the CNCF ecosystem. |
| 180 | qubership-opensearch-monitoring | qubership-infra opensearch, saqs |
✅ | Observability and Analysis | Monitoring | Prometheus, Thanos, VictoriaMetrics | The provided file describes a service that collects metrics from an OpenSearch cluster using custom scripts. This functionality falls under the 'Observability and Analysis' category in the CNCF landscape, specifically under the 'Monitoring' subcategory. The service is similar to other monitoring solutions like Prometheus, Thanos, and VictoriaMetrics, which also collect and analyze metrics from various sources. |
| 181 | qubership-opentelemetry-helm-charts | qubership-observability observability |
✅ | Observability and Analysis | Tracing | Jaeger, Zipkin, SkyWalking | The provided file describes configurations for the OpenTelemetry Operator, which is a part of the OpenTelemetry project. OpenTelemetry is a set of APIs, libraries, agents, and instrumentation to enable observability in cloud-native applications. It falls under the 'Observability and Analysis' category in the CNCF landscape, specifically under the 'Tracing' subcategory, as it is primarily used for distributed tracing. Alternatives like Jaeger, Zipkin, and SkyWalking are also prominent CNCF projects in the same subcategory, providing similar functionalities for distributed tracing. |
| 182 | qubership-pipelines-cli-command-samples | qubership-devops |
❌ | ⛅ | ⛅ | ⛅ | |
| 183 | qubership-pipelines-common-python-library | qubership-devops |
✅ | App Definition and Development | Continuous Integration & Delivery | Tekton, Argo Workflows, Jenkins X | The provided file describes 'Quubership Pipelines Common Library', which is a Python library providing clients and wrappers for common devops services like Jenkins, MinIO, and GitLab Pipelines. This suggests it is used in the context of CI/CD workflows. The CNCF category 'App Definition and Development' with subcategory 'Continuous Integration & Delivery' fits best, as the library is designed to facilitate CI/CD processes. Alternatives like Tekton, Argo Workflows, and Jenkins X are also CI/CD tools within the CNCF landscape that serve similar purposes. |
| 184 | qubership-pipelines-declarative-executor | qubership-devops |
❌ | ⛅ | ⛅ | ⛅ | |
| 185 | qubership-pipelines-modules-ops | qubership-devops |
✅ | App Definition and Development | Application Definition & Image Build | Tekton, Argo Workflows, Jenkins X | The file name 'qubership-pipelines-modules-ops' suggests that the solution is related to pipelines and modules, likely for CI/CD or workflow automation. This aligns with the 'App Definition and Development' category in the CNCF landscape, specifically under 'Application Definition & Image Build'. Alternatives like Tekton, Argo Workflows, and Jenkins X are also pipeline solutions within the CNCF landscape that fit this category. |
| 186 | qubership-profiler-agent | qubership-ossf-request broadcast-pilot, observability, profiler |
❌ | n/a ❌ | n/a ❌ | n/a ❌ | The provided content describes a plugin for instrumenting HTTP context in Tomcat <= 9.x, WildFly <= 26.x, and Spring Boot <= 2.x, but it does not provide enough information to categorize it within the CNCF landscape. The CNCF landscape primarily focuses on cloud-native technologies like container orchestration, service meshes, monitoring, and logging, whereas this plugin seems to be specific to Java web servers and frameworks. Therefore, it does not clearly fit into any CNCF category or subcategory. |
| 187 | qubership-prometheus-adapter-operator | qubership-ossf-request monitoring, observability |
❌ | n/a ❌ | n/a ❌ | n/a ❌ | The provided content describes a directory containing configuration and templates for generating HTML/Markdown documentation of an AMS operator's custom resource definitions, using the 'gen-crd-api-reference-docs' project. However, it does not provide enough information to clearly determine a specific CNCF category or subcategory. The content seems related to documentation generation for Kubernetes CRDs, but without more details about the tool's functionality or purpose, a precise classification is not possible. The 'gen-crd-api-reference-docs' project itself is not listed in the CNCF landscape, and no clear alternatives can be suggested based on the given information. |
| 188 | qubership-query-exporter | qubership-infra |
✅ | Observability and Analysis | Monitoring | Prometheus, Thanos, Cortex | The file name 'qubership-query-exporter' suggests that this is a tool related to exporting queries, likely metrics or logs, which is a common functionality in monitoring solutions. Given the CNCF landscape, this would best fit under 'Observability and Analysis' with a subcategory of 'Monitoring'. Alternatives like Prometheus, Thanos, and Cortex are well-known CNCF projects that handle metrics collection, storage, and querying, making them suitable alternatives. |
| 189 | qubership-renovate-config | qubership-devops |
❌ | n/a ❌ | n/a ❌ | The provided content is insufficient to determine the category or subcategory within the CNCF landscape. The text 'qubership-renovate-config' does not provide enough context about the solution's purpose, functionality, or components to make an accurate classification. More information is needed to identify similar solutions in the CNCF landscape. | |
| 190 | qubership-repo-template | qubership-devops |
✅ | App Definition and Development | Application Definition & Image Build | Helm, Kustomize, Jsonnet | The provided file describes a repository template named 'qubership-repo-template' which is likely used for defining and managing Kubernetes application deployments. Based on the CNCF landscape, this fits best under 'App Definition and Development' with a subcategory of 'Application Definition & Image Build' as it seems to be a tool or template for defining applications. Alternatives like Helm, Kustomize, and Jsonnet are also used for similar purposes in managing Kubernetes applications. |
| 191 | qubership-spark-on-k8s | qubership-infra |
❌ | ⛅ | ⛅ | ⛅ | |
| 192 | qubership-tcp-duplicator | qubership-ossf-request logging, observability |
✅ | Networking | Service Proxy | Envoy, Linkerd, NGINX | The solution described is a TCP proxy that mirrors data to configured servers, which aligns with the networking category in the CNCF landscape. Specifically, it falls under the 'Service Proxy' subcategory as it acts as an intermediary for TCP traffic. Alternatives like Envoy, Linkerd, and NGINX are also service proxies that handle traffic routing and mirroring, making them suitable comparisons. The solution's focus on TCP-level operations without higher-level protocol support further justifies this categorization. |
| 193 | qubership-test-pipelines | qubership-devops |
✅ | App Definition and Development | Continuous Integration & Delivery | Argo CD, Flux, Tekton | The provided file describes a GitHub Action that verifies Kubernetes deployments, including status checks, log collection, and test validation. This functionality aligns with Continuous Integration & Delivery (CI/CD) tools in the CNCF landscape, which focus on automating and validating deployments. Alternatives like Argo CD, Flux, and Tekton are also CI/CD tools that manage and verify Kubernetes deployments, making them suitable comparisons. The category 'App Definition and Development' was chosen as it encompasses tools that assist in defining, deploying, and verifying applications in cloud-native environments. |
| 194 | qubership-testing-platform-adapter-robot-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 195 | qubership-testing-platform-auth-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 196 | qubership-testing-platform-common-auditing-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 197 | qubership-testing-platform-common-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 198 | qubership-testing-platform-configuration-dataset-excel-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 199 | qubership-testing-platform-crypt-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 200 | qubership-testing-platform-datasets | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 201 | qubership-testing-platform-diameter-transport-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 202 | qubership-testing-platform-environments | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 203 | qubership-testing-platform-export-import-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 204 | qubership-testing-platform-integration-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 205 | qubership-testing-platform-itf-core-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 206 | qubership-testing-platform-itf-executor | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 207 | qubership-testing-platform-itf-lite-backend | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 208 | qubership-testing-platform-itf-reporting | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 209 | qubership-testing-platform-itf-stubs | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 210 | qubership-testing-platform-macros-core-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 211 | qubership-testing-platform-multitenancy-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 212 | qubership-testing-platform-ram | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 213 | qubership-testing-platform-ss7-transport-library | qubership-tp |
❌ | ⛅ | ⛅ | ⛅ | |
| 214 | qubership-trino | qubership-infra |
❌ | ⛅ | ⛅ | ⛅ | |
| 215 | qubership-version-exporter | qubership-ossf-request monitoring, observability |
✅ | Observability and Analysis | Monitoring | Prometheus Operator, Thanos, VictoriaMetrics | The solution described, 'qubership-version-exporter', is a tool that collects version information from various sources (Postgres, HTTP, ConfigMaps, and Secrets in Kubernetes) and exports them as Prometheus metrics. This fits squarely within the 'Observability and Analysis' category of the CNCF landscape, specifically under 'Monitoring', as it deals with collecting and exposing metrics for monitoring purposes. Alternatives like Prometheus Operator, Thanos, and VictoriaMetrics are also focused on monitoring and metrics collection, making them comparable solutions. |
| 216 | qubership-workflow-hub | qubership-devops |
✅ | App Definition and Development | CI/CD | Argo Workflows, Tekton, Jenkins X | The provided file describes a set of workflows and actions that automate various tasks such as building, testing, and deploying applications, managing releases, and handling pull requests. These functionalities align with CI/CD (Continuous Integration and Continuous Deployment) tools, which are part of the 'App Definition and Development' category in the CNCF landscape. The alternatives listed (Argo Workflows, Tekton, Jenkins X) are also CI/CD tools that provide similar automation capabilities for cloud-native applications. |
| 217 | qubership-zookeeper | qubership-infra saqs, zookeeper |
❌ | n/a ❌ | n/a ❌ | n/a ❌ | The provided content is insufficient to determine the CNCF category or subcategory. It mentions using integration tests based on the Robot Framework, but this does not clearly align with any specific CNCF category. The Robot Framework itself is a generic test automation framework and is not specifically tied to cloud-native technologies. More context about the solution's purpose, architecture, or deployment environment would be needed to make a proper classification. |
| 218 | release-drafter | qubership-devops |
❌ | ⛅ | ⛅ | ⛅ | |
| 219 | robot-shop | qubership-observability example, observability |
✅ | App Definition and Development | Application Testing | Locust, JMeter, Gatling, k6 | The provided file describes a load generation tool that is used to test applications by simulating multiple clients and varying load over time. This fits well within the 'Application Testing' subcategory of the 'App Definition and Development' category in the CNCF landscape. Alternatives like Locust, JMeter, Gatling, and k6 are also load testing tools that are commonly used in the cloud-native ecosystem for similar purposes. |