Liongard Overview — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Liongard Overview (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.
Liongard is an automated IT documentation and configuration management platform built for Managed Service Providers (MSPs). It continuously inspects and documents IT environments across hundreds of technology platforms, providing:
Liongard replaces manual documentation processes with automated, scheduled inspections that capture the state of servers, firewalls, cloud services, and more.
of software per customer site that runs inspections against many targets. It is not a per-endpoint monitor and reports nothing about the machine it sits on. For endpoint agents use atera-agents, syncro-assets, ncentral-devices, or immybot-endpoint-management; in halopsa-agents an agent is a human technician.
detects; it does not remediate. Action belongs to the RMM (ncentral-monitoring-tasks, superops-runbooks, immybot-script-execution) or the PSA.
straight to liongard-environments, liongard-inspections, liongard-systems, or liongard-detections.
Environments represent customer organizations or sites being monitored. Each environment contains agents, launchpoints, systems, and detections, and can be organized into groups and tiers for logical management. See references/api.md for the environment core field table.
Agents are lightweight software deployed to customer sites that execute inspections. Each agent connects back to the Liongard platform and runs configured inspection tasks on a schedule.
Inspectors are templates defining what to inspect. Liongard provides hundreds of built-in inspectors for common platforms:
Launchpoints are configured inspection instances that tie together an inspector template, a target environment, an agent, credentials, and a schedule. They represent "run this inspector against this target on this schedule."
| Component | Description |
|---|---|
| Inspector | What to inspect (template) |
| Environment | Where it belongs (customer) |
| Agent | Who runs it (deployed software) |
| Credentials | How to authenticate to the target |
| Schedule | When to run (cron expression) |
Systems are discovered items from inspections. When a launchpoint runs, it discovers systems such as servers, firewalls, cloud services, user accounts, and other entities. Each system contains detailed configuration data captured during inspection.
Detections are automated change and anomaly alerts generated when inspections find differences from previous runs. They enable MSPs to:
Custom metrics allow MSPs to define and track specific values across systems and environments. Metrics can be evaluated per-system or aggregated across environments.
The timeline provides an audit trail of all events and changes within Liongard, including inspection runs, detection triggers, user actions, and system events.
Dataprints provide JMESPath-evaluated data extraction from system details. They allow precise querying of nested configuration data captured during inspections.
Asset Inventory (v2) provides identity and device profile management across all inspected environments, aggregating user accounts and devices discovered through inspections.
Liongard uses API key authentication via the X-ROAR-API-KEY header:
GET /api/v1/environments
X-ROAR-API-KEY: YOUR_API_KEY
Content-Type: application/jsonRequired Headers:
| Header | Value | Description |
|---|---|---|
X-ROAR-API-KEY | {api_key} | API key from Liongard portal |
Content-Type | application/json | For POST/PUT requests |
Liongard uses instance-based URLs where each customer has a unique subdomain:
https://{instance}.app.liongard.com/api/v1
https://{instance}.app.liongard.com/api/v2For example, if your instance is acmemsp:
https://acmemsp.app.liongard.com/api/v1/environmentsexport LIONGARD_INSTANCE="yourcompany"
export LIONGARD_API_KEY="your-api-key-here"The complete v1 and v2 endpoint catalogs, pagination parameter table, and full filter-operator table live in references/api.md. The conventions worth knowing up front:
page / pageSize query params; POST-based query endpoints take a nested PascalCase Pagination: {Page, PageSize} object in the body. Default pageSize is 50, max is 2000.Data, TotalRows, HasMoreRows, CurrentPage, TotalPages, PageSize. Loop on HasMoreRows rather than computing page counts.fields[] for field selection plus orderBy: [{path, direction}] for sorting. Operators: eq, ne, gt, lt, gte, lte, contains, in.Retry-After on 429 and add jitter to backoff.See references/examples.md for reusable pagination, retry-with-backoff, and error-handling client implementations, and references/errors.md for the HTTP status code table.
Environment (ID)
|
+-- Agents (AgentID)
| +-- Installer Generation
|
+-- Launchpoints (LaunchpointID)
| +-- Inspector (InspectorID)
| +-- Schedule (Cron)
| +-- Systems (SystemID)
| +-- System Details
| +-- Dataprints
| +-- Inspections (InspectionID)
|
+-- Detections (DetectionID)
|
+-- Metrics (MetricID)
| +-- Metric Evaluations
|
+-- Timeline Events
|
+-- Asset Inventory
+-- Identities
+-- Device Profiles~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.