A cross platform forensic parser written in Rust!
C-Rank Grade: A (Welcoming) - 55/100
External PR Merge Rate: 100%
Response Time: -
First Timer Success: 100%
puffyCid/artemis has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in puffyCid/artemis respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 54.7 places puffyCid/artemis in the A tier.
The external contributor pull request merge rate for puffyCid/artemis is 100.0%, based on public PR activity from non-core contributors.
puffyCid/artemis currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in puffyCid/artemis welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/puffyCid/artemis?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~57 hours (96% approval). Large PRs (>500 lines) take ~421 hours (45% approval). Keep your diff compact for rapid review.
Its probably worth moving the macOS emond artifact to the Artemis API. Its is a legacy artifact and was removed in macOS Ventura. The artifact is also just a handful of plist files so its easy to parse with the artemis API
What new feature do you think would be cool to add to artemis? Right now artemis only has one feature flag yarax. Currently it is enabled by default. It would be nice if other parts of artemis were hidden behind feature flags that could be enabled or disabled at compile time Describe the solution you'd like Try to add feature flags for: BoaJS GCP Azure AWS API network boaJS "sandbox" Parquet (requires #420)
What new feature do you think would be cool to add to artemis? Timestamps for XML Schedule Tasks are stored in the Registry. Right now artemis only supports extracting timestamps when run on a Windows system. However, it should be easy to add support to get timestamps if a user provides a path to an offline/copied SOFTWARE file from the same system as the XML tasks file Describe the solution you'd like Add option to provide alternative path to SOFTWARE Registry file Additional context N/A
What new feature do you think would be cool to add to artemis? Currently artemis has a large number of unit tests and every artifact has one or more integration tests. However, one test area that artemis does not do very well is validation of the output. The integration tests at forensics/tests should also read the output files and verify that the output is correct and expected Describe the solution you'd like A few artifacts have had output formats change a bit. Hopefully by adding output validation it can help ensure updated output formats are correct. Additional context Triage, Windows Services, and Schedule Tasks integration tests have been updated to validate output data
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to puffyCid/artemis, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of puffyCid/artemis acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
puffyCid/artemis has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 54.7 places puffyCid/artemis in the Welcoming tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, puffyCid/artemis currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for puffyCid/artemis are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.