glider-trace-runtime — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited glider-trace-runtime (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use GliderTrace when working in a C# or .NET repository and the task needs runtime evidence rather than static source inspection alone.
Prefer GliderTrace for test runs, command runs, failure summaries, exception and stack evidence, stdout/stderr summaries, counters, traces, dumps, GC dumps, and artifact indexing. Use trace_status first when you need to confirm server state, workspace, artifact root, allowed commands, and local dependency availability.
For investigations, run commands through trace tools so stdout, stderr, exit status, timings, findings, and artifacts remain connected to one session. Use test-specific tools for .NET test evidence, and query/export session artifacts when summarizing the failure or handing evidence back to the user.
Use plain shell commands only for simple file operations or when captured runtime evidence is not useful.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.