Cairnlytics
Compliance-ready, non-intrusive risk scoring for open-source dependencies and supply-chain collapse.
Market Need
Modern software depends heavily on open-source components, creating systemic risk when widely used libraries become unmaintained, patch slowly or accumulate security debt. Existing CVE scans and ad-hoc reviews can miss development-health signals such as maintainer concentration, community engagement and patch responsiveness.
Growing expectations around operational resilience, third-party governance and software bills of materials are also exposing a due-diligence gap. Open-source projects often have no vendor, audit site, SOC 2 pack or financial checks, leaving security and compliance teams without defensible evidence of dependency resilience.
Solution
Cairnlytics provides automated, data-driven risk scoring for open-source dependencies. Users submit repository URLs, package names and versions, or a software bill of materials. The platform constructs direct and transitive dependency graphs and calculates a dynamic Cairn Index risk score out of 1,000 for each component using development-health and governance signals from repository history.
- Continuously updates scores as project activity, maintainership and governance change.
- Highlights dependencies most likely to create failure or compromise across recursive supply chains.
- Supports alerts for indicators such as abandoned projects or suspicious maintainer changes.
- Uses Git metadata and repository history without accessing source-code contents or sensitive internal systems.
- Provides dashboards and evidence to support remediation, portfolio oversight, audits and regulatory reporting.
Target Market
- Chief information security officers and security teams.
- Software developers and engineering teams.
- Procurement, risk and compliance teams requiring auditable open-source and third-party risk evidence.
Status
- Live proof-of-concept clickable prototype.
- Demonstrates Cairn Index scoring, trend visualisation and dependency-depth analysis from repository or package inputs.
Needs
- Pilot partners willing to share software bills of materials and validate scoring against real incident and maintenance histories.
- Support to harden the prototype into a minimum viable SaaS platform.
- Development of integrations, monitoring, alerting and reporting capabilities.