- Industry
- IT Company
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- Engineering Manager
- Code
- ENG-17
It keeps open-source libraries, base images and runtimes patched across the SaaS platform and client codebases under support contracts, checking each against security advisories, end-of-life dates and the open-source licence policy. It decides which updates to merge, batch or hold, and blocks any copyleft licence that would conflict with a client's ownership of the code.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the source code repository and CI/CD: dependency manifests, advisories, licence data and test results for the repositories named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the source code repository and CI/CD: it opens or merges the update pull requests as decided. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The dependency policy: patch deadlines, the open-source licence policy and client IP clauses, end-of-life dates, and the software bill of materials rules.
Reads from
the source code repository and CI/CD: dependency manifests, advisories, licence data and test results for the repositories named.
Acts in
the source code repository and CI/CD: it opens or merges the update pull requests as decided.
Hands back
A list of updates, each with repository, package, to_version, decision (merge, batch, hold or block), reason, licence_ok (true or false) and due (YYYY-MM-DD or null).
Asks a person when
An update brings a licence not in MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, is a major version, or touches a client codebase outside its support scope.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Merge by itself up to | patch | Updates up to this level merge when tests pass. |
| Security patch within (days) | 7 | A fix for a known vulnerability ships within this. |
| Allowed licences | MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC | Comma-separated. Anything else needs the approver; copyleft is blocked in client-owned code. |
| Least release age (days) | 3 | Non-security releases younger than this wait. |
| Warn before end of life (days) | 90 | Runtimes reaching end of life within this get an upgrade plan. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Merge updates up to patch when tests pass; others go to review.
- Ship security fixes within 7 days.
- Allow only MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC; a copyleft licence in code the client owns under the SOW is blocked.
- Wait 3 days on non-security releases.
- Plan upgrades for anything reaching end of life within 90 days and update the software bill of materials.
See the Dependency Management Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.