Stars and mentions
Last 30 days, Oct 5 – Nov 3
Package downloads
Top repositories
Dadoum’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside Dadoum’s account where Dadoum opened or reviewed pull requests in the past 365 days.
Who noticed Dadoum
Everyone who starred or forked Dadoum’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
- Gold
- 01st place finishes
- Silver
- 02nd place finishes
- Bronze
- 03rd place finishes
- Awarded repositories
- 0Owned by Dadoum now
No trending awards yet
None of the repositories Dadoum owns has finished in the top three of a completed trending day or week, by stars, forks or PR authors. See who is trending now.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Apple rejecting anisette servers (-80045): SideStore, GSAPort, more Since around Oct 12-13, Apple’s GrandSlam auth has been rejecting login attempts that use headers from anisette-v3-server, failing with -80045 (“This action cannot be completed at this time”) during the SRP init step. What’s affected - Public anisette servers running anisette-v3-server (SideStore’s, StikStore’s, and a bunch of community ones all fail the same way) - SideStore, iloader, and AltStore/AltServer users who rely on a remote anisette server - GSAPort (the jailbreak tweak that backports Apple’s GSA to iOS 5+) will also stop working while this is broken What's known - Every remote v3 server tested returns -80045 - Headers generated locally on a physical Mac (via AOSKit) still work - The issue reporter’s theory is that Apple added new detection aimed at the virtualized macOS / Docker fingerprint these servers use. That’s a theory, not confirmed. - The issue is still open and the maintainer hasn’t responded yet What you can do for now - If you have a real Mac, use local anisette generation instead of a remote server - Don’t keep hammering logins on your Apple ID. Repeated failed attempts won’t fix this and aren’t worth the risk - Watch the issue for updates: anisette-v3-server#61