Ikarus AI LabsInstrument B · Evidence Plane 2
OpenPulse — Software Ecosystem Intelligence
An evidence-based intelligence system for understanding meaningful changes in the open-source software ecosystem.
OPEN SOURCEOpenPulse on GitHub ↗
Question
What changed upstream, what evidence establishes the change, and does it actually apply to the software we depend on?
Inequalities
Distinctions OpenPulse keeps explicit
RELATED ≠ AFFECTED
A related advisory does not mean your version is affected.
UNKNOWN ≠ NOT AFFECTED
Missing evidence is reported as unknown, never as clear.
MATCH STRENGTH ≠ EVIDENCE STRENGTH
A confident identity match is not a confident finding.
SOURCE SIGNAL ≠ ACTIONABLE INTELLIGENCE
Raw upstream signals need interpretation and applicability.
Scope
Evidence OpenPulse reasons about
- identity resolution
- lifecycle intelligence
- support changes
- upstream changes
- vulnerability evidence
- registry evidence
- applicability
- evidence confidence
- temporal reasoning
- first detection
- effective dates
- uncertainty
- provenance
OpenPulse is not an end-of-life database or a generic software composition analysis tool. It studies how upstream change becomes evidence, and when that evidence actually applies.