Skip to content

casework / CASE

active 2023-08-172026-07-24 (UTC)

Complete coverage26,518 / 26,518 hourly files (100%) · 2 absent upstream2023-08-152026-08-23 (UTC)
Events
356
Pushes
71
Pull requests
71
Issues
9
Stars
17
Forks
4

Activity over time

Daily event counts in the loaded window

Line chart, 1073 days from 2023-08-17 to 2026-07-24. Pushes: 71 total, peak 9 in a day. Pull requests: 71 total, peak 5 in a day. Issues: 9 total, peak 2 in a day. Comments: 70 total, peak 4 in a day. Stars: 17 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
ajnelson-nist126353452
plbt59834312
vulnmaster15066
chrishargreaves7006
sbarnum4004
eoghanscasey2200

Recent activity

Latest issues, pull requests and releases

  • Issue#189vulnmaster2026-01-11 19:56
    Adopting CASE Investigation Ontology by Communities with Defined Business Rules
  • Issue comment#188plbt52026-01-02 20:21
    Can the definition of core:Event be updated to support past events (including hypothesised ones)?
  • Issue comment#183ajnelson-nist2025-12-30 20:03
    Issue 178 addition of CASE investigation:Investigator subclasses
  • Issue comment#187chrishargreaves2025-12-09 12:15
    Add Analyst Role to CASE
  • Issue comment#184plbt52025-12-03 07:52
    Add Technician Role Class to CASE
  • Issue comment#186ajnelson-nist2025-12-02 23:15
    Issue #184 - Add investigation:Technician role class
  • Issue comment#186vulnmaster2025-12-02 23:09
    Issue #184 - Add investigation:Technician role class
  • Issue comment#184ajnelson-nist2025-11-28 19:54
    Add Technician Role Class to CASE
  • Issue comment#187vulnmaster2025-10-23 03:41
    Add Analyst Role to CASE
  • Issue#187vulnmaster2025-10-23 03:39
    Add Analyst Role to CASE
  • Issue#187vulnmaster2025-10-23 03:39
    Add Analyst Role to CASE
  • Pull request#186vulnmaster2025-10-22 15:52
  • Pull request#186vulnmaster2025-10-22 15:52
  • Pull request#186vulnmaster2025-10-22 15:52
  • Pull request#186vulnmaster2025-10-22 15:52
  • Pull request#186vulnmaster2025-10-22 15:52
  • Issue comment#184vulnmaster2025-10-22 13:16
    Add Technician Role Class to CASE
  • Issue comment#185vulnmaster2025-10-17 13:37
    Notation in SOLVE-IT for CASE classes that do not yet exist
  • Issue comment#185vulnmaster2025-09-29 17:28
    Notation in SOLVE-IT for CASE classes that do not yet exist
  • Issue#185chrishargreaves2025-09-29 15:28
    Notation in SOLVE-IT for CASE classes that do not yet exist
  • Pull request#183vulnmaster2025-09-24 00:42
  • Issue comment#179chrishargreaves2025-09-09 09:50
    Add representation for KeywordSearchResult and potentially KeywordIndex
  • Issue comment#182chrishargreaves2025-09-08 13:55
    What is the correct representation for a message recipient?
  • Issue comment#182ajnelson-nist2025-09-08 13:14
    What is the correct representation for a message recipient?
  • Issue comment#178ajnelson-nist2025-08-26 16:46
    Addition of Investigator Subclasses

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 17 stars here means stars gained during the window, not the repo's star count.