Git Branching Strategy: Trunk-Based vs GitFlow for Teams
Trunk-based development or GitFlow? Compare Git branching strategies for outsourced and offshore teams, with a decision table and rules that keep releases safe.
How to manage open-source dependencies safely: lockfiles, updates, vulnerability scanning and licence checks, plus what to require from an outsourced team.
Modern applications are mostly assembled, not written. A typical web or mobile project pulls in hundreds of open-source packages once you count the dependencies of your dependencies. That is efficient, but it means much of your running code was written by people you have never met, and a flaw or a malicious change in any one package can reach your product.
For a CTO or founder who outsources development, dependency management is a practical risk that is easy to overlook. This guide explains what to control and what to ask your delivery team for.
Every project should commit a lockfile (such as package-lock.json, yarn.lock, poetry.lock, Podfile.lock or Gemfile.lock). A lockfile records the exact version of every direct and indirect dependency, so the build on a developer laptop, in CI and in production uses the same code.
Practical rules:
npm ci) rather than a command that may resolve new versions.Teams that update rarely tend to update dangerously. A better pattern is small, frequent, automated updates:
Run dependency scanning in the pipeline on every pull request and on a schedule, because new vulnerabilities are disclosed against code you shipped months ago. Most package ecosystems and hosting platforms offer built-in audit commands or free scanners, and commercial tools add reachability analysis and reporting.
Agree a policy before the first alert arrives:
| Severity | Suggested response |
|---|---|
| Critical, exploitable in your usage | Fix or mitigate immediately, treat as an incident |
| High | Fix in the current sprint |
| Medium | Schedule within an agreed window |
| Low or not reachable | Track, review at the next update cycle |
The exact windows are a business decision, but writing them down avoids debate under pressure. Scanning complements, rather than replaces, deeper checks described in our comparison of penetration testing and vulnerability scanning.
A software bill of materials (SBOM) is a machine-readable inventory of the components inside your application. Standard formats such as SPDX and CycloneDX exist, and many build tools can generate one automatically. Enterprise buyers, regulators and security questionnaires increasingly ask for them, and having one also speeds up your response when a new vulnerability makes headlines: you can search the inventory instead of guessing.
Alongside the SBOM, run an automated licence check and agree which licence families are acceptable. Flag anything unusual for legal review before it ships.
When working with an external team, put dependency practices into the contract or statement of work and ask for evidence rather than promises:
Include these in your vendor evaluation and review them as part of handover, so you inherit a codebase you can maintain.
Dependency hygiene works best when it is built into the delivery pipeline from day one. Our cloud and DevOps services cover automated pipelines, scanning and release controls, and our software testing team builds the regression suites that make frequent updates safe. If you want an independent review of an existing codebase or a team that treats supply chain security as a default, contact us to discuss your project.
Trunk-based development or GitFlow? Compare Git branching strategies for outsourced and offshore teams, with a decision table and rules that keep releases safe.
Monorepo or polyrepo? Compare code repository strategies for web, mobile and backend products, with a decision table and tips for outsourced teams.
How to version and retire APIs without breaking clients: versioning options, breaking-change rules, sunset policies and a checklist for outsourced teams.
Tell us about your platform, your product idea or the systems you want to modernise. Someone from our Chennai engineering team will get back to you personally.