PAGES
← all tools
◆ Integrated & IT Risk Management

RiskShard

v0.11.1 open-source

RiskShard audits public cyber-loss reports, recording what each one actually publishes across four statistical questions, with every answer pinned to a quoted source.

Summary

RiskShard is an open-source cyber tool that audits public cyber-loss reports to document what specific statistical measures each source publishes, pinning every answer to the source passage for verification. It does not require installation and operates by reading documentation directly, positioning itself as an alternative to manual source reading in the integrated-risk-management space. It is aimed at those who must cite risk figures, like consultants or risk managers, and the project has seen 9 releases in the tracking period, with the last update occurring 17 days ago.

RiskShard audits public cyber-loss reports, recording what each one actually publishes across four statistical questions, with every answer pinned to a quoted source.

How RiskShard helps

Does the loss figure I am about to cite actually give a most-likely value, or only an average?

looks up the source in the audited set and reports which of the four measures it publishes, quoting the exact passage — or states plainly that the source never says

Is the population behind this number even the one I think it is?

checks whether the source discloses which countries, industries or company sizes were measured, and pins that answer to the quoted text so you can see who was actually counted

Does this report tell me how the risk is spread, or just hand me one number?

records whether the source shows a distribution of losses at all, distinct from giving a single average or median

Can this source tell me how often losses exceed a given size?

records whether the source publishes any exceedance statement, so you know if it can support a "losses bigger than X happen Y% of the time" claim

How much is a shard's answer really resting on the biggest loss in the data?

flags entries whose stated figures lean on the maximum observed value rather than a distribution, so you can see when "up to $X" is standing in for a real estimate

Has anyone already read this report, or am I the first?

looks the source up against the audited list and either returns the pinned, quoted answers already on file or tells you it hasn't been read yet, so you know whether to trust a figure or go read it yourself

all 14 features, with the evidence for each →

Languages

Not documented

Features

14 capabilities · 3 backed by code, an API document or a real run

Built from RiskShard's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What RiskShard offers you

  • Command-line interface3
  • JSON data export1
  • Python scripting support1
All capabilities 14 capabilities
Anchor composition breakdown shipped Partitions each shard's per-event mean across its three anchors using the beta-PERT mean identity, surfacing how much of a figure each anchor contributes in explorer items, the executive report's trust section, and the citation. 6 releases · first seen Sep 2026

release

  • Publishes Finding 10 in docs/FINDINGS.md, showing that anchor weighting by contribution to the final figure diverges sharply from a raw count: three shards are 92%, 92%, and 98.8% measured on impact while drawing 100% of their frequency mean from an out-of-population source. v0.11.0 · Sep 2026 · source · release history
  • The citation surface now refuses to emit a figure without the full anchor-composition breakdown. v0.11.0 · Sep 2026 · source · release history
  • Adds engine/composition.py to partition each shard's per-event mean across its three anchors using the beta-PERT mean identity, exposing how much of a figure each anchor contributes.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v0.11.0 · Sep 2026 · source · release history
  • Surfaces anchor composition in three places: each explorer item, the executive report's How much to trust it section, and the citation — which now refuses to emit a figure without the breakdown. v0.11.0 · Sep 2026 · source · release history
  • Adds engine/composition.py, which partitions each shard's per-event mean across its three anchors using the beta-PERT mean identity, exposing the breakdown on each explorer item, the executive report's How much to trust it section, and the citation. v0.11.0 · Sep 2026 · source · release history
  • Adds Finding 10 (documented in docs/FINDINGS.md): flags that a count of anchors and a weighting by contribution disagree about the same corpus, surfacing that no shard is well-anchored on both the impact and frequency families simultaneously. v0.11.0 · Sep 2026 · source · release history
Blocked-but-held source diagnostic shipped Cross-references every source the audit cannot read against extracted titles in the intake register, and fails the doctor check when a document is on disk but not being read. 3 releases · first seen Aug 2026

release

  • Adds engine.intake.blocked_but_held diagnostic that cross-references every source the audit cannot read against extracted titles in the intake register, failing the doctor on any match where a document is on disk but not being read.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v0.11.1 · Sep 2026 · source · release history
  • Adds engine.intake.blocked_but_held check, which compares every source the audit cannot read against the extracted title of every document in the intake register and fails the doctor on a match. v0.11.1 · Sep 2026 · source · release history
  • Adds access_mode: manual_download to source declarations, preventing automated fetching of gated documents and requiring disk-based acquisition with an acquisition field v0.10.0 · Aug 2026 · source · release history
Cyber-loss report audit shipped Audits public cyber-loss reports to document which statistical measures each report actually publishes, with findings pinned to document hashes and quoted passages. 1 release · 2 other sources · first seen Sep 2026

Also counts toward: JSON data export

release

  • Ships data pack data_pack_releases/2026.08.23-v0.11.0.json alongside the engine update. v0.11.0 · Sep 2026 · source · release history

docs

  • Audits public cyber-loss reports to document what statistical measures each actually publishes, with every figure pinned to a source hash and quoted passage.
  • Audits public cyber-loss reports to document what statistical measures each actually publishes, pinned to document hashes with quoted passages.
Evidence integrity verification shipped Verifies the integrity of evidence packs and contributor configurations before simulations or submissions. 2 releases · 1 other source · first seen Jul 2026

Also counts toward: Command-line interface

release

  • exceedance_basis is now required on any record anchoring an impact.max constraint; previously missing or default values will break validation. v0.6.0 · Aug 2026 · source · release history
  • Adds validate_evidence, contributor_preflight, and doctor commands to verify evidence integrity and contributor configuration v0.1.0 · Jul 2026 · source · release history

example

  • Verify the integrity of the current evidence pack before running simulations. riskshard validate_evidence v0.1.0 · Jul 2026 · source
Shard impact diagnostics verified Reports whether a shard's maximum impact value has been exceeded and how much of a shard's answer depends on that maximum, helping users understand the statistical shape of loss estimates. 1 release · 2 other sources · first seen Aug 2026

release

  • Adds exceedance_basis field (values: modeled_quantile, observed_rank, population_ceiling, none_known) to records anchoring an impact.max constraint v0.6.0 · Aug 2026 · source · release history

command line

  • exceedance — Does a shard's impact.max say anything about being exceeded? (ADR-0008) v0.6.0 · Aug 2026 · command-line history
  • tail — How much of a shard's answer rests on its maximum? (ADR-0008) v0.6.0 · Aug 2026 · command-line history
Multi-domain Monte Carlo simulations shipped Enables running Monte Carlo loss simulations for business email compromise, data breach, ransomware, insider misuse, and AI-enabled fraud across 8 countries. 3 releases · first seen Jul 2026

release

  • Retires four Australian ransomware country bridges, relabeling the shard as governed_starter v0.3.0 · Aug 2026 · source · release history
  • Adds Statistics Canada CSCSC full-cell readings for frequency and NetDiligence insured-claims anchors for impact in Canada risk modelling v0.3.0 · Aug 2026 · source · release history
  • Enables running Monte Carlo loss simulations for business email compromise, data breach, ransomware, insider misuse, and AI-enabled fraud across 8 countries v0.1.0 · Jul 2026 · source · release history
Manual source acquisition mode shipped Prevents automated fetching of gated documents and requires disk-based acquisition with an explicit field, supporting manual download workflows. 2 releases · first seen Aug 2026

release

  • Adds access_mode: manual_download to source declarations, preventing automated fetching of gated documents and requiring disk-based acquisition with an acquisition field v0.10.0 · Aug 2026 · source · release history
  • Adds url_stability field (values: dated, rolling) to all source records and enforces matching during artifact gathering v0.2.0 · Aug 2026 · source · release history
Annotated evidence entry verified Lets users attach optional prose notes to evidence entries and strength-ledger entries, recording the reason a count changed when the cause was a measurement change rather than new evidence, with the notes rendered beneath the public Progress table. 2 other sources · first seen Aug 2026

command line

  • --note — Optional prose recorded with the entry and rendered beneath the public Progress table. Use it whenever a count moves because the measurement changed rather than the evidence. v0.9.0 · Aug 2026 · command-line history
  • --ledger-note — Optional prose recorded with the strength-ledger entry and rendered beneath the public Progress table. Use it whenever a count moves because the measurement changed rather than the evidence. v0.9.0 · Aug 2026 · command-line history
Distribution table printing shipped Prints the impact and composited loss distribution tables using a helper script. 1 release · 1 other source · first seen Aug 2026

Also counts toward: Command-line interface, Python scripting support

release

  • Introduces python scripts/riskshard_modules.py tail command to print the impact distribution table v0.6.0 · Aug 2026 · source · release history

example

  • Print the composited loss distribution table using the new helper script. python scripts/riskshard_modules.py tail v0.6.0 · Aug 2026 · source
Contributor configuration validation shipped Checks if local configuration meets contributor standards and validates configuration before submitting risk shards. 1 release · 1 other source · first seen Jul 2026

Also counts toward: Command-line interface

release

  • Adds validate_evidence, contributor_preflight, and doctor commands to verify evidence integrity and contributor configuration v0.1.0 · Jul 2026 · source · release history

example

  • Check if your local configuration meets contributor standards before submitting a risk shard. riskshard contributor_preflight v0.1.0 · Jul 2026 · source
Non-interactive demo mode shipped Runs the full tool demo end-to-end without requiring user interaction. 2 other sources · first seen Jul 2026

example

  • Verify the integrity of the current evidence pack before running simulations. riskshard validate_evidence v0.1.0 · Jul 2026 · source
  • Run full demo non-interactively printf 'demo\nexit\n' | python scripts/riskshard_console.py
Parameter provenance lookup shipped Shows the full provenance trail for any given parameter, letting users trace where a value came from. 2 other sources

example

  • Show provenance for a parameter python scripts/riskshard_modules.py provenance <shard> <parameter>
  • Show all parameters with sources and caveats python scripts/riskshard_modules.py provenance --all
Staging workflow verified Provides a stage command to move evidence or entries through a defined workflow step. 1 other source · first seen Aug 2026

command line

Progress ledger shipped Generates and maintains a public Progress table that tracks evidence counts and strength over time. 1 other source

example

  • Regenerate progress ledger table python scripts/strength_ledger.py markdown

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for RiskShard, 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 →

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 RiskShard 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…

Explore the full chart →

Releases

Show

7 entries

  1. September 20262
  2. August 20264
  3. July 20261
    Show

    7 entries

    Project health

    Issue, contributor and maintainer activity in raviaxo/RiskShard, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 1 +1 vs prior 12 months
    2. Maintainers 1 +1 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 0% of issues opened, last 12 months
    5. Median time to close 53 days first maintainer reply 53 days
    6. Open backlog 5 of 15 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 5
    3. Contributors / month 1
    4. Commits / month 6
    5. Stars 3
    Issue themes, last 12 months
    • other 100%

    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

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →