Florian Harwoeck (@harwoeck)
  • Stars
    star
    39
  • Global Rank 406,458 (Top 15 %)
  • Followers 45
  • Following 75
  • Registered almost 9 years ago
  • Most used languages
    Go
    100.0 %
  • Location πŸ‡¦πŸ‡Ή Austria
  • Country Total Rank 1,861
  • Country Ranking
    Go
    64

Top repositories

1

afy

The simplest artifact repository manager out there. Really.
Go
13
star
2

adapt

πŸ“¦ adapt is a simple general-purpose migration library that gets embedded into your Go application
Go
4
star
3

mysophie

mysophie is a tool that handles static asset versioning and can be plugged into any building process. It's stateless, allows very aggressive cache settings and only runs once per production build.
Go
3
star
4

ipstack

πŸ“‘ ipstack is a helper package for calling the https://ipstack.com API. It includes type-safe response packets and a WorkerPool for asynchronous, once-only, lookup tasks.
Go
3
star
5

magic

🎠 magic is an auto-parsing library and competitive coding helper package with batteries included. The library takes care of allocating and populating your memory.
Go
3
star
6

apperr

πŸ—‘ apperr provides a unified framework- and network-agnostic error generation interface. Errors can be localized and converted to GRPC, Twirp, HTTP, etc. equivalents
Go
2
star
7

fscache

πŸ‘“ fscache is a simple, non-magical helper package for loading file-system content only once and using an in-memory cache for consecutive requests.
Go
2
star
8

azoo

azoo is a headless ASVS Level 3 Identity and Access Management (IAM) system built for a cloud-native environment
Go
2
star
9

hibpoffline

High-performance Service for querying an offline copy of the HIBP database (a collection of 551 million breached πŸ”“ passwords). Exists because private ☁️ = ❀.
1
star
10

fcer

fcer is a file partition algorithm, that splits a file into a set of partitions and calculates their offset and length. After finding these parts it is possible to process a file concurrently without worker-interference.
Go
1
star
11

liblog

Discontinued in favor of log/slog. liblog was an interface/contract for logging backends. It was used by public libraries and packages that wanted to give their user's control over structured and leveled logging output.
Go
1
star