ENGINEERING
Weekly Slack digest of newly introduced dependency licenses
Once a week, compares this week's license inventory against last week's, and posts a Slack digest listing every newly introduced license type, which repos pulled it in, and flags…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionRead current and prior week license snapshotsPostgres
- LogicDiff snapshots for newly introduced licenses
- LogicClassify each new license by risk tier
- OutputPost grouped license digest to SlackSlack
What it does
Gives engineering leadership a regular, readable pulse on license drift. On a weekly schedule it reads the current set of dependency licenses across repositories, diffs it against the prior week's snapshot, and posts a Slack message summarizing what's new: each freshly introduced license, the repos and packages responsible, and a prominent callout for anything copyleft or forbidden.
When to use it
Use it when you want lightweight visibility without opening a dashboard, or to keep a compliance channel informed week over week. It surfaces emerging risk early, before a formal audit, and keeps the whole team aware of what's entering the dependency tree.
How it works
- 1A weekly schedule triggers the digest.
- 2The flow reads the current week's license inventory from Postgres and the prior snapshot.
- 3It computes the set difference to find newly introduced license types and packages.
- 4A check classifies each new license as allowed, copyleft, or forbidden.
- 5It posts a formatted Slack digest grouping new licenses by risk, with policy breaches pinned at the top.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.