Skip to content
GitHub Explorer

Erasmus-In-Salerno/.github

View on GitHub ↗Related repositories →

README file for the Erasmus in Salerno organization

active 2024-10-14 → 2025-01-08 (UTC)

Complete coverage26,411 / 26,411 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-19 (UTC)
Events
38
Pushes
5
Pull requests
0
Issues
31
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 87 days from 2024-10-14 to 2025-01-08. Pushes: 5 total, peak 2 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 31 total, peak 8 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 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
Janna3319000
awrockla12400
Lnola5100

Recent activity

Latest issues, pull requests and releases

  • Issue#16awrockla2025-01-08 10:06
    re-analyze test coverage and quality with jacoco and pitest after #12
  • Issue#12awrockla2025-01-08 10:06
    automatically generate testcases for poorly tested classes (with randoop and github copilot)
  • Issue#18awrockla2025-01-08 10:06
    find vulnerable dependencies with OWASP DC
  • Issue#19awrockla2025-01-05 12:37
    Presentation for our report/project
  • Issue#15Lnola2025-01-05 03:33
    performance testing: micro benchmark for greedy methods
  • Issue#6Lnola2025-01-05 03:33
    sonarcloud: reduce cognitive complexity of methods
  • Issue#7Lnola2024-12-29 18:13
    build CI/CD pipeline / github actions
  • Issue#9Lnola2024-12-29 18:13
    dockerize the project
  • Issue#17Janna332024-12-25 17:38
    security analization with OWASP FindSecBugs
  • Issue#18Janna332024-12-16 17:57
    find vulnerable dependencies with OWASP DC
  • Issue#17Janna332024-12-13 10:27
    security analization with OWASP FindSecBug & OWASP DC
  • Issue#16Janna332024-12-06 12:21
    re-analyze test coverage and quality with jacaco and pitest after #12
  • Issue#10Janna332024-12-06 12:20
    analyze code coverage with jacoco
  • Issue#15Janna332024-11-29 10:30
    performance testing: micro benchmark for greedy methods
  • Issue#14awrockla2024-11-25 11:40
    add the published db-utils to our webapp
  • Issue#13awrockla2024-11-25 11:39
    publish our db-utils_repo inside our repo
  • Issue#8awrockla2024-11-24 15:10
    web app / java application
  • Issue#12Janna332024-11-22 19:37
    automatically generate testcases for poorly tested classes (with randoop and github copilot)
  • Issue#11Janna332024-11-22 19:37
    analyze test cases by mutation testing with pitest
  • Issue#10Janna332024-11-22 19:37
    analyze code coverage with jacoco
  • Issue#5Janna332024-10-25 19:51
    create constant for string literal duplication
  • Issue#9Janna332024-10-25 11:07
    dockerize the project
  • Issue#8Janna332024-10-25 11:07
    web app / java application
  • Issue#7Janna332024-10-25 11:06
    build CI/CD pipeline / github actions
  • Issue#6Janna332024-10-25 10:49
    reduce cognitive complexity of methods

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