SECOPS
Nightly audit of license drift across all repositories
On a nightly schedule, scans every tracked repository's dependency tree for newly appeared copyleft licenses since the last run and posts a consolidated drift report to a SecOps…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionResolve license trees across all reposGitHub
- LogicDiff against prior snapshot for new copyleft
- OutputPost consolidated drift report to SecOpsSlack
What it does
PR-time gates only catch changes going forward, and only on repos that have the check wired up. This workflow sweeps your whole fleet on a schedule. Every night it walks each configured GitHub repository's default branch, resolves the full dependency tree's licenses, and compares the result against the previous night's snapshot. Any package that newly carries a copyleft license — whether freshly added, version-bumped into a relicensed release, or surfaced by a transitive change — shows up as drift. It then assembles one digest: repository, package, old vs. new license, and a link to the dependency manifest.
When to use it
Use it as the backstop for organizations with many repositories where you cannot assume every project enforces a PR-time license check. It catches relicensing events (a dependency that was MIT last quarter and is GPL today) and drift in repos that predate your gating policy.
How it works
- 1A scheduled trigger runs nightly.
- 2The workflow iterates the configured repositories, resolving each dependency tree's licenses from GitHub.
- 3A logic step diffs current licenses against the stored prior snapshot to isolate newly copyleft packages and persists the new snapshot.
- 4If any drift is found, it posts a consolidated report to the SecOps Slack channel; a clean night posts nothing.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.