by Imagile

28 integrations · three verification levels · one auth bar

Every tool behind one pasted token.

Each integration is its own command area, signs in with a long-lived token you generate once in the vendor's UI, and returns the same JSON envelope. Nothing needs a browser login at use time.

  1. unit

    Shipped, with its logic tested against stubbed HTTP. Never run against a real instance.

  2. live

    Run against a real instance; its common commands work there.

  3. stable

    In routine use against real instances, with its commands and output settled.

Work tracking and source

Where the work is described, discussed and reviewed.

  • toil jira unit

    Jira Data Center

    Issues, search, transitions, comments, worklogs, attachments, custom fields, boards, sprints

    Credential Personal access token

  • toil jira-cloud unit

    Jira Cloud

    Issues, search, transitions, comments, worklogs, attachments, custom fields, projects, users, boards, sprints

    Credential Atlassian account email and API token

  • toil ado unit

    Azure DevOps Server

    Work items, repos, pull requests, pipelines

    Credential Personal access token

  • toil ado-cloud unit

    Azure DevOps Services

    Work items, repos, pull requests, comments, votes

    Credential Organization-scoped personal access token

  • toil bitbucket unit

    Bitbucket Data Center

    Repositories, pull requests, comments, builds

    Credential HTTP access token

  • toil bitbucket-cloud unit

    Bitbucket Cloud

    Repositories, pull requests, comments, builds, Pipelines

    Credential Atlassian API token with Bitbucket scopes, or an access token

  • toil github unit

    GitHub & GitHub Enterprise

    Pull requests, reviews, issues, projects, checks

    Credential Fine-grained PAT

  • toil confluence unit

    Confluence Data Center

    Pages, spaces, search, comments, labels, attachments

    Credential Personal access token

  • toil confluence-cloud unit

    Confluence Cloud

    Pages, spaces, search, comments, labels, attachments

    Credential Atlassian account email and API token

  • toil git unit

    Local git

    Status, diff, log, branches, commit report

    Credential None — local

Build, release and runtime

Where code becomes something running.

  • toil jenkins unit

    Jenkins

    Jobs, builds, console logs, queue

    Credential API token

  • toil artifactory unit

    JFrog Artifactory

    Repositories, artifact search, versions, licenses

    Credential Access token

  • toil openshift unit

    OpenShift / Kubernetes

    Pods, events, logs, metrics, deployments

    Credential Service account token

  • toil splitio unit

    Split.IO

    Feature flags, environments, change requests

    Credential Admin API key

  • toil saucelabs unit

    Sauce Labs

    Test jobs, builds, real devices and device sessions, tunnels, platforms, app storage, teams

    Credential Username and access key

Security and quality

The scanners and gates every change has to clear.

  • toil sonar unit

    SonarQube

    Quality gates, issues, hotspots, measures

    Credential User token

  • toil checkmarx unit

    Checkmarx One

    Projects, scans and scan results statistics

    Credential API key, exchanged over HTTP

  • toil contrast unit

    Contrast Security

    Applications, vulnerability findings, libraries

    Credential API key + service key

  • toil sonatypeiq unit

    Sonatype IQ Server

    Applications, organizations, policies, policy evaluations

    Credential User token pair

  • toil sde unit

    SD Elements

    Projects, countermeasures, threats, users

    Credential API token

  • toil osv unit

    OSV.dev

    Known vulnerabilities for a dependency inventory, from the public OSV database

    Credential None — public API

  • toil ossindex unit

    Sonatype OSS Index

    Known vulnerabilities for a dependency inventory, from Sonatype's public index

    Credential Account username and API token

Observability

What production is actually doing.

  • toil dynatrace unit

    Dynatrace

    Problems, entities, traces

    Credential Access token

  • toil logscale unit

    Falcon LogScale

    Log queries, repositories

    Credential Personal API token

  • toil elasticsearch unit

    Elasticsearch

    Search, count, indices, cluster health

    Credential API key

  • toil kibana unit

    Kibana

    Status, spaces, dashboards, data views, alerting rules

    Credential API key

Design and data

The context engineers pull in from outside the code.

  • toil figma unit

    Figma

    Files from a link, comments, version history

    Credential Personal access token

  • toil alation unit

    Alation

    Catalog metadata, search, documents

    Credential Refresh token, exchanged over HTTP

Dependency analysis

One command per source. You compose.

No single command quietly asks four services on your behalf. Build an inventory locally, then pipe it to exactly the sources you trust, and every finding says where it came from.

compose 
$ toil deps scan | toil osv vulns
$ toil deps scan > inventory.json
$ toil sonatypeiq evaluate --from inventory.json --application-id payments-api
CommandSourceCoversNetwork
toil deps scan Local manifests Package inventory for npm, Maven and NuGet None
toil deps diff Local manifests Packages added, removed or changed between two refs None
toil osv vulns OSV.dev Known vulnerabilities for an inventory Public API
toil ossindex vulns Sonatype OSS Index Known vulnerabilities for an inventory Public API
toil sonatypeiq evaluate Sonatype IQ Server Policy evaluation against an application Your server
toil deps frisk --source <one> The source you name Alias for the matching command above As above
toil deps outdated JFrog Artifactory Newer versions in your mirrors Your server
toil deps license-check JFrog Artifactory License metadata for an inventory Your server

Not planned

Some tools can't clear the bar.

If the only workable sign-in is a password, an interactive login, or another CLI, toil won't integrate it, however useful it would be.

  • ServiceNow

    Personal access tokens are opt-in and usually disabled, so in practice sign-in falls back to a username and password.

  • IBM UrbanCode Deploy

    There is no standalone personal token; the only workable sign-in is an account password.