osdfir-infrastructure
osdfir-infrastructure-2.16.0 open-sourceFree plan: not checked yet · Open source: yes
The section your link pointed to isn't on osdfir-infrastructure's page any more, so we've brought you to the top.
OSDFIR Infrastructure simplifies deploying and integrating open source digital forensics tools to Kubernetes clusters using Helm.
What you can do now
Summary
osdfir-infrastructure is an open-source DFIR deployment framework that packages forensic and incident-response services as Helm charts for Kubernetes, with no paid license. It is run by Kubernetes operators or DFIR teams in local or cloud clusters, using configurable charts rather than installing each service separately. The deployment can combine Timesketch, Yeti, OpenRelik, GRR, HashR, and dfTimewolf, with integrations linking investigative timelines, threat intelligence, collection, and processing workflows. Its README places it in the open-source digital forensics infrastructure space; ongoing releases cover authentication, ingress, storage, and multi-instance deployments.
OSDFIR Infrastructure simplifies deploying and integrating open source digital forensics tools to Kubernetes clusters using Helm.
How osdfir-infrastructure helps
Which forensic and incident-response services can my Kubernetes cluster run together?
deploys supported components such as Timesketch, Yeti, OpenRelik, GRR, HashR, and dfTimewolf as integrated Helm-chart components, though the available services depend on the chart configuration
How can I connect forensic collection, processing, and investigation across my environment?
links dfTimewolf recipes, OpenRelik workflows and artifact storage, GRR remote collection, and Timesketch analysis so processed evidence can move between stages
Where can responders correlate forensic timelines with threat intelligence?
provides Timesketch for collaborative timeline analysis and connects it with Yeti, which stores and analyzes observables, tactics, techniques, and campaigns
Can I run separate investigation environments in the same Kubernetes cluster?
supports multiple Timesketch instances and multiple Turbinia instances, allowing distinct deployments within one cluster
How can I preserve or reuse storage and configuration that my cluster already manages?
lets deployments attach existing persistent volume claims and provide existing Timesketch or Turbinia configuration rather than relying only on chart-generated defaults
How do I expose these investigation services securely to my users?
provides configurable ingress, single-host access, external URLs, OIDC authentication for selected services, identity-aware proxy support for OpenRelik, and certificate options through self-signed certificates or cert-manager; the exact protection depends on the configured ingress and authentication settings
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for osdfir-infrastructure, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail osdfir-infrastructure puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
40 entries
No entries match these filters.
- November 20261
- September 20261
- August 20261
- July 20261
- June 20261
- May 20262
- March 20261
- February 20263
- January 20263
- December 20251
- November 20252
- August 20253
- May 20251
- April 20252
- February 20251
- September 20244
- June 20245
- May 20241
- April 20241
- March 20242
- January 20243
Project health
Issue, contributor and maintainer activity in google/osdfir-infrastructure, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors not measured distinct committers, last 12 months
- Maintainers not measured core set, last 12 months
- Bus factor not measured committers behind half the commits
- Community-filed 22% of issues opened, last 12 months
- Median time to close 2.2 years first maintainer reply 51 days
- Open backlog 6 of 66 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 6
- Contributors / month not measured
- Commits / month not measured
- Stars not measured
- bugs 33%
- features 67%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.