IPED
4.3.1 open-sourceThe section your link pointed to isn't on IPED's page any more, so we've brought you to the top.
IPED is an open source tool that processes and analyzes digital evidence seized at crime scenes by law enforcement or in corporate investigations.
java -jar iped.jar --webapi --host=localhost --port=8080 --sources=sources.json
[
{
"id": "case1",
"path": "/data/iped-cases/case-2024-001"
}
]
# Create a bookmark for suspicious executables
curl -X POST http://localhost:8080/bookmarks/suspicious
# Search for executables referencing passwords or encryption
curl 'http://localhost:8080/search?q=type:exe+AND+(content:password+OR+content:encrypted)'
# Add matched docs to the bookmark (supply the docs JSON array from search results)
curl -X PUT http://localhost:8080/bookmarks/suspicious/add \
-H 'Content-Type: application/json' \
-d '[{"source":"case1","id":42}]'
iped -s "-field1:xxx -field2:yyy"
iped --continue <path_to_case>
iped --restart <path_to_case>
Summary
IPED is an open-source digital forensics tool that processes and analyzes digital evidence gathered during investigations, distributed for free under an open-source license. It runs as a desktop application, either built from source or installed from a release, and can operate from the command line for batch processing or through an integrated analysis GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands., with cases portable enough to run from removable drives. It is aimed at law enforcement examiners and corporate investigators handling disk images, mobile extractions, and file systems, rather than at general IT or SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. teams. It sits in the digital forensics and incident responsedigital forensics and incident responseDigital forensics and incident response, investigating what happened during a security incident and containing it. The work includes preserving evidence, reconstructing activity and restoring systems. category, offering carving, indexing, timeline analysis, and parsers for chat apps like WhatsApp and Telegram, comparable to commercial forensic suites though built and maintained openly. First committed in 2015, it has 76 contributors and remains actively developed, with 561 commits and 10 releases in the past year.
IPED is an open source tool that processes and analyzes digital evidence seized at crime scenes by law enforcement or in corporate investigations.
How IPED helps
Which chat messages, calls, and contacts can I recover from a phone extraction or disk image?
parses formats like WhatsApp, Telegram, Skype, BitTorrent, and Threema directly from UFDR, AD1, or disk image containers, surfacing decoded conversations, quoted replies, and status changes in the analysis interface
Which files can I pull back out of damaged or unallocated space?
carves 40+ file formats including video, image, and archive types straight from raw disk sectors, without relying on file system metadata
Does this collection of images contain child exploitation material?
runs a dedicated CSAM detection profile combining local and remote classifiers against every image and video extracted from the case
Who is talking to whom, and when, across everything seized in this case?
builds a unified timeline across parsed evidence with event filtering and graph analysis linking communications between contacts
Can I search a hundred million seized items for a name, number, or phrase fast enough to matter?
indexes the whole case for regex search with OCR, face recognition, and similar-document matching, built to hold up at up to 400GB/h and 135 million items
Are two photos of the same object or person, taken years apart, actually connected?
matches faces across the case with recognition and age estimation, and flags visually similar images even when file names or metadata differ
Languages
Command line
No command matches.
| 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 IPED, 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 IPED 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
28 entries
No entries match these filters.
- October 20261
- March 20261
- December 20251
- April 20251
- December 20241
- April 20241
- August 20231
- June 20231
- April 20231
- March 20231
- February 20231
- July 20221
- June 20222
- February 20221
- December 20211
- October 20211
- August 20211
- June 20211
- May 20211
- March 20211
- November 20201
- October 20201
- August 20201
- July 20202
- December 20192
Project health
Issue, contributor and maintainer activity in sepinf-inc/IPED, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 28 +9 vs prior 12 months
- Maintainers 5 +1 joined · −0 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 45% of issues opened, last 12 months
- Median time to close 10 days first maintainer reply 2.8 hours
- Open backlog 314 of 1,672 issues ever filed
- Issues opened / month 2 · 2 communitymaintainers
- Open backlog 314
- Contributors / month 7
- Commits / month 19
- Stars 2,953
- bugs 30%
- features 33%
- questions 1%
- docs 1%
- other 35%
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.