Activity
Stars and mentions · Last 30 days, Oct 7 – Nov 5
Top repositories
piercefreeman’s repositories ranked by new forks, as on trending.
Contributes to
Repositories outside piercefreeman’s account where piercefreeman opened or reviewed pull requests in the past 365 days.
Who noticed piercefreeman
Everyone who starred or forked piercefreeman’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.
Achievements
Awards earned by the repositories piercefreeman owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
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
Show HN: Waymark – A workflow engine that compiles jobs instead of replaying piercefreeman/waymark
Show HN: Waymark – A workflow engine that compiles jobs instead of replaying comments · posted on 2026.11.05 at 09:06:31 (c=0, p=5)
Show HN: Waymark – A workflow engine that compiles jobs instead of replaying Discussion
Show HN: Waymark – A workflow engine that compiles jobs instead of replaying Hey everyone! @mozgiii and I have been working on Waymark for the better part of the last year. Waymark’s an open source durable execution library with similar functionality to Temporal or DBOS. A few unique design decisions: — Write jobs in normal code (right now Python but JS coming soon). Instead of running control flow as-is, which requires booting up an interpreter to replay past state, we’ll just compile your code directly. We walk your AST and map your logic to our stackless VM bytecode. We support variables, conditionals, await, sleep, helper functions, loops... basically what you’d expect in workflow logic. — Since we’re compiling a language subset, we can proactively flag errors in your workflows locally instead of when they run in production. — It only requires Postgres as the task broker. We’ve spent a lot of time tuning our design to play nicely with its strengths and limitations; our current benchmarks show around 1500 workflows/second but we still have some more optimization work to do here. — Actions plug-and-play with FastAPI’s dependency injection syntax. So if you already have an ecosystem based on typehinting/DI, it should fit like a glove. It allows for parallelization of workflows across one machine or a whole cluster. The bulk of the work per node is done by our central Rust core - which distributes workflows to properly saturate all cores. The idea is to be as batteries included as possible with the broker, webapp, and runtime. What to use it for? It works great as the runner loop controlling agents, but it also works well for basically any task that you need to kick off in the background. It’s largely replaced our way of writing api code. Most frontend actions at this point just push to a simple REST endpoint that kick off a background job. I spent an embarrassing amount of time making our waymark.sh site interactive - it’s probably the best place to learn more. We’re starting with Python support and looking for community input on what language to ship next. Would love to hear your thoughts!
There's just no excuse not to give your OSS project some personality now: piercefreeman/trustme
Free and open source, of course. Give it a try: piercefreeman/TrustMe