ENGINEERING
Weekly audit of every Hugging Face model license in the repo
On a schedule, it scans the codebase for all referenced Hugging Face models, re-checks each one's current license against policy.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionScan repo for all HF model IDsGitHub
- ActionFetch current license per modelHugging Face
- LogicFlag violations and license changes vs snapshot
- OutputPost compliance digest to SlackSlack
What it does
Catches license drift over time. A model that was permissively licensed when you added it can change its license, become gated, or have its model card updated. This workflow re-inventories every Hugging Face model your repo references and reports any that no longer comply.
When to use it
Use it as a standing compliance backstop alongside per-PR gates. PR checks catch new additions; this catches the slow drift of dependencies you already shipped. Ideal for monthly legal reviews or SOC 2 / audit evidence.
How it works
- 1A scheduled trigger runs the workflow weekly.
- 2The repository is scanned to build the full list of referenced Hugging Face model IDs.
- 3The Hugging Face API fetches the current license and gated status for each model in the inventory.
- 4A logic step compares the live licenses to your allowlist and to the last recorded snapshot, flagging new violations and license changes.
- 5A Slack message delivers a digest to the engineering channel listing compliant counts and any flagged models with details.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.