Skip to content

Timmilytim/Spring-Security-Jpa-Practice

View on GitHub โ†—Related repositories โ†’

This is a shit code I practiced with, if you want to use it, you'll have to create your own database for it because, there is no sign up API, only login, you should know what your table structure would look like from the User.java class, if you have questions about it, my contacts are on my profile.... Sharp!! ๐Ÿ˜‰๐Ÿ˜Ž

active 2025-07-27 โ†’ 2025-07-27 (UTC)

Complete coverage26,546 / 26,546 hourly files (100%) ยท 2 absent upstream2023-08-15 โ†’ 2026-08-25 (UTC)
Events
2
Pushes
0
Pull requests
0
Issues
0
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 1 days from 2025-07-27 to 2025-07-27. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 0 total, peak 0 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

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

Nobody pushed, opened or commented here in the loaded window โ€” this repo's activity is stars and forks only.

Recent activity

Latest issues, pull requests and releases

No issue or PR events โ€” this repo's activity is pushes only.

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.