Skip to content

IBM/codenet-minerva-code-analyzer

View on GitHub ↗Related repositories →

Java source code (and/or binary) to JSON based system dependency graph generator.

active 2023-12-132025-02-05 (UTC)

Partial coverage18,257 / 23,386 hourly files (78%) · 2 absent upstream · 5,127 failed, retryable2023-12-122026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
197
Pushes
40
Pull requests
49
Issues
17
Stars
3
Forks
3

Activity over time

Daily event counts in the loaded window

Line chart, 421 days from 2023-12-13 to 2025-02-05. Pushes: 40 total, peak 5 in a day. Pull requests: 49 total, peak 8 in a day. Issues: 17 total, peak 3 in a day. Comments: 9 total, peak 5 in a day. Stars: 3 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

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

ContributorContributionsPushesPRsComments
rahlk8734327
sinha108203120
rangeetpan9340
fabio-franco3001
scottkurz3001
rofrano1010

Recent activity

Latest issues, pull requests and releases

  • Issue#106rahlk2025-02-05 05:16
    Add artifactory deployment to github actions after every release
  • Issue#105rahlk2025-02-05 05:15
    Run Integration tests in github actions before release of a new version
  • Pull request#104rahlk2025-02-05 05:03
  • Issue#102rahlk2025-02-01 16:21
    Create comprehensive comment analysis capabilities
  • Issue#101rahlk2025-02-01 16:15
    Add a support to be able to capute static and instance initialization blocks in Java classes
  • Issue#100rahlk2025-02-01 16:04
    Extend Codeanalyzer to Capture Database Entries
  • Pull request#96rahlk2025-01-22 05:47
  • Releasegithub-actions[bot]2025-01-18 04:40
    v1.0.9
  • Pull request#92rahlk2025-01-18 04:39
  • Issue comment#88rahlk2025-01-16 02:23
    Code analyzer fails when gradle wrapper is in the project (gradlew)
  • Issue comment#88fabio-franco2025-01-16 01:19
    Code analyzer fails when gradle wrapper is in the project (gradlew)
  • Issue comment#88rahlk2025-01-15 23:59
    Code analyzer fails when gradle wrapper is in the project (gradlew)
  • Issue comment#92rahlk2025-01-15 23:57
    Fix issue 87 and 88
  • Pull request#92rahlk2025-01-15 23:53
  • Issue comment#91rahlk2025-01-15 23:49
    Get Cyclomatic complexity measures at Analysis Level 1.
  • Issue#91rahlk2025-01-15 23:49
    Get Cyclomatic complexity measures at Analysis Level 1.
  • Issue#91rahlk2025-01-15 23:49
    Get Cyclomatic complexity measures at Analysis Level 1.
  • Pull request#89rahlk2025-01-15 23:42
  • Issue comment#89rahlk2025-01-15 23:41
    Cyclomatic complexity analysis level 1
  • Issue comment#88rahlk2025-01-15 22:35
    Code analyzer fails when gradle wrapper is in the project (gradlew)
  • Releasegithub-actions[bot]2024-12-03 01:46
    v1.0.7
  • Pull request#81rahlk2024-12-03 01:45
  • Pull request#81rahlk2024-12-03 01:45
  • Issue comment#79rahlk2024-12-03 01:42
    It seems that code analyzer assumes that gradle projects always has a wrapper(gradlew)
  • Issue#79rahlk2024-12-03 01:42
    It seems that code analyzer assumes that gradle projects always has a wrapper(gradlew)

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