ImmyBot Software Deployment — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ImmyBot Software Deployment (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.
This is ImmyBot's headline capability. The model is desired-state: you assert what should be installed, then a maintenance session brings the endpoint into compliance. This skill walks the canonical deployment workflow end-to-end.
| Tool | Purpose |
|---|---|
immybot_software_list | Per-tenant software catalog |
immybot_software_list_global | Global ImmyBot software catalog |
immybot_software_search | Search by name |
immybot_software_get | Full detail for one software |
immybot_software_versions | Available versions for a software |
immybot_software_latest_version | The current "latest" version |
immybot_software_categories | Browse by category |
immybot_software_publishers | Browse by publisher |
immybot_software_stats | Usage stats across the fleet |
| Tool | Purpose |
|---|---|
immybot_deployments_list | Current deployments |
immybot_deployments_get | Detail for a deployment |
immybot_deployments_create | Assert new desired state |
immybot_deployments_for_computer | Deployments scoped to a computer |
immybot_deployments_for_software | Deployments scoped to a software |
immybot_deployments_compliance | Compliance report for a deployment |
immybot_deployments_trigger | Force immediate reconciliation (destructive) |
immybot_software_install | Install a software via desired state (destructive) |
| Tool | Purpose |
|---|---|
immybot_maintenance_sessions_list | Recent sessions |
immybot_maintenance_sessions_get | One session snapshot |
immybot_maintenance_sessions_start | Start a session (destructive) |
immybot_maintenance_sessions_pause | Pause a running session |
immybot_maintenance_sessions_resume | Resume a paused session |
immybot_maintenance_sessions_cancel | Cancel a session |
immybot_maintenance_sessions_logs | Log stream |
immybot_maintenance_sessions_results | Final outcome |
immybot_maintenance_sessions_active | Currently active sessions |
immybot_maintenance_sessions_summary | Summary metrics |
| Tool | Purpose |
|---|---|
immybot_computers_list | Enrolled computers |
immybot_computers_get | One computer detail |
immybot_computers_search | Search by name |
immybot_computers_inventory | Installed software on a computer |
immybot_computers_deployments | Deployments hitting a computer |
immybot_computers_trigger_checkin | Force a check-in |
immybot_software_search → immybot_software_get → immybot_software_latest_versionConfirm the software exists in the catalog and what version you intend to deploy.
For tenant-wide rollouts:
immybot_tenants_get → immybot_tenants_computersFor a single computer:
immybot_computers_search → immybot_computers_getCall immybot_deployments_create with the chosen software, version, and scope. The deployment now exists, but nothing has happened on the endpoint yet.
Either wait for the next scheduled maintenance window, or trigger immediately:
immybot_maintenance_sessions_startThis is destructive — get human approval first.
Poll immybot_maintenance_sessions_get and tail immybot_maintenance_sessions_logs. Stop polling once the session is in a terminal state.
Call immybot_deployments_compliance to see which computers in scope reached the desired state and which failed.
immybot_computers_get for the computerimmybot_computers_inventory for installed softwareimmybot_computers_deployments for what desired-state expectsimmybot_tenants_getimmybot_tenants_compliance for the rollupimmybot_deployments_complianceimmybot_maintenance_sessions_listimmybot_maintenance_sessions_results for outcomeimmybot_maintenance_sessions_logs for the failing log linesimmybot_tasks_logs for lower-level detailversion or track latest. Always confirm which mode you are in before changing the desired version.
software on the same scope can fight. Use immybot_deployments_for_computer to spot conflicts before adding a new one.
sessions handle this, but expect the session to span longer than the install itself.
fleet-wide software; reserve per-computer for exceptions.
fleet-wide maintenance session.
expected outcome.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.