SECOPS
Block PRs that pull in copyleft-licensed dependencies
On every pull request, scans changed dependency manifests for newly added packages, flags any GPL/AGPL/copyleft license.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened or updatedGitHub
- ActionResolve licenses of newly added dependenciesGitHub
- LogicMatch licenses against copyleft denylist
- OutputPost comment and set failing commit statusGitHub
What it does
This workflow turns license compliance into a hard merge gate. Whenever a pull request touches a dependency manifest (package.json, requirements.txt, go.mod, Cargo.toml, and friends), it diffs the lockfile to find packages that are genuinely *new* to the tree, resolves each one's SPDX license, and compares it against your forbidden list. If a copyleft license such as GPL-2.0, GPL-3.0, AGPL-3.0, or SSPL appears, the PR's status check goes red and a comment is posted that names the package, version, license, and which manifest introduced it. Permissively licensed additions (MIT, Apache-2.0, BSD) pass silently.
When to use it
Use it on any proprietary codebase where shipping copyleft code would create a redistribution obligation your legal team has not approved. It is the safety net for teams that move fast and merge often, where a single transitive dependency can quietly drag in an AGPL package nobody reviewed.
How it works
- 1A GitHub pull request trigger fires on open and synchronize events.
- 2The workflow fetches the changed manifest and lockfile diff to isolate newly introduced packages, then resolves each package's SPDX license from the registry metadata.
- 3A logic step checks every resolved license against the configured copyleft denylist.
- 4If any match, GitHub posts a review comment listing each offending package and version, and the workflow sets a failing commit status that blocks merge.
Tune the denylist and allowlist to match your legal policy.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.