glim

A TUI for monitoring GitLab CI/CD pipelines and projects

Not yet testedsource: GitHubRustMITcommit cd53dae9985c

Rust, MIT licensed. The project labels itself: ci cd, gitlab api, monitoring, ratatui and tui.

glim has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
234
forks
15
open issues
17
watchers
4
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

  • ratatui verified to run · Rust · 2 shared topics
  • witr verified to run · Go · 2 shared topics
  • goaccess verified to run · C · 2 shared topics
  • bottom verified to run · Rust · 2 shared topics
  • trippy verified to run · Rust · 2 shared topics
  • gitlogue verified to run · Rust · 2 shared topics

Run history

No recorded runs.

Topics (from GitHub)

ci-cdgitlab-apimonitoringratatuitui

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/glim.svg)](https://argusic.com/subject/glim)

Questions

Does glim run?
glim has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test glim?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for glim?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion