Auvik Networks — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Auvik Networks (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.
A network in Auvik is an IP scope - typically a subnet that Auvik has discovered devices on. An interface is a port on a device. Both are distinct entity types with their own list endpoints. This skill clarifies the data model and the relationships.
| Tool | Use For |
|---|---|
auvik_networks_list | List networks for a tenant |
auvik_networks_get | Detail for one network |
auvik_interfaces_list | List interfaces for a tenant |
Fields you'll see:
networkName - usually the subnet in CIDR formnetworkType - private, internet, unknownscanStatus - whether discovery scans for this network are healthygatewayIp, dhcpEnableddescription - free-form, often blankNetworks are not VLANs in the Auvik model - VLAN information lives on interface records and switch configurations. A single VLAN typically maps to a single network, but the network entity is keyed on subnet, not VLAN ID.
Fields you'll see:
interfaceName - e.g. GigabitEthernet1/0/24interfaceType - ethernet, wireless, virtual, loopback, tunnel, etc.adminStatus - up or down - operator-setoperStatus - up or down - actual current statelinkSpeed - in bpsparentDeviceId - the device that owns the interfacedescription - administrator-set port description (when populated)| adminStatus | operStatus | Meaning |
|---|---|---|
| up | up | Healthy |
| up | down | Link down - real condition (flap, cable, upstream) |
| down | down | Administratively shut down - usually deliberate |
| up | testing | In test mode - transient |
A flapping interface will move between up and down on operStatus while adminStatus stays up. Capacity and statistics tools only return useful data for up/up interfaces.
parentDeviceId -> auvik_devices_getauvik_devices_get_details)There is no direct "list devices in this network" call - you list devices, list networks, and join on IP membership client-side.
auvik_networks_list - count, list IP ranges.scanStatus for each - any in error state is a discovery problem.auvik_interfaces_list for the tenant.adminStatus = up, operStatus = down.parentDeviceId.auvik_statistics_interface over a short window to see flap frequency.entityId with entityType = interface.parentDeviceId.auvik_devices_get on the parent for the human-readable context.auvik_interfaces_list alongside physical ones. Their interfaceType distinguishes them. For capacity reporting, exclude interfaceType in {loopback, tunnel, virtual} unless the question is specifically about them.linkSpeed is 0 for down interfaces on some platforms - guard against divide-by-zero in utilization math.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.