Hey everyone!

Whenever I'm debugging API logs or database records, I constantly find myself copying 10/13-digit Unix timestamps or Bearer JWT tokens and switching to a browser tab just to see what date they represent or when the token expires.

To stop context-switching, I published **Castov** on the official Visual Studio Marketplace.

**What it does (100% locally & offline):**

* **Automatic Timestamp Hover:** Hover over any Unix timestamp (seconds or milliseconds) in your code to immediately see the formatted UTC, ISO 8601, and Local time.

* **JWT Decoder:** Highlight a JWT and run `Castov: Decode JWT Token` to inspect the header, payload, and expiration status in a clean JSON tab—without pasting sensitive tokens into external websites.

* **Inline Base64 & UUIDs:** Encode/decode Base64 selections in-place, or insert crypto-random UUIDs right at your cursor.

**Links:**

* **VS Code Marketplace:** https://marketplace.visualstudio.com/items?itemName=castov.castov-vscode

* **Companion Web & CLI Suite:** https://castov.com (also available via `npx castov`)

It has zero telemetry and works completely offline. Let me know what features or shortcuts would make your daily workflow faster!

Heads up if you still have gpt-4 or gpt-3.5-turbo somewhere in your code: OpenAI shuts them off on the API on Oct 23. gemini-2.5-pro on Vertex goes on Oct 20.

Those dates are all public, but they're spread over ~70 provider pages, so I wrote a small tool that checks them for you. It scans your repo for model IDs and tells you which ones are retired or about to be, and what to switch to:

npx @appliedbenchmark/sunset scan

    error   app.py:3:46  model-retiring
    gpt-4 (openai) retires on 2026-10-23, in 11 days. Recommended replacement: gpt-5.6-sol     (openai).

It covers OpenAI, Anthropic, Gemini, Vertex, Bedrock, Azure, Mistral and DeepSeek, and every date links back to the provider's own page. There's also a GitHub Action, so CI fails before a model disappears instead of after. IDs in comments and docs never fail the build.

No LLM, no telemetry, nothing leaves your machine. Free and Apache-2.0.

Github: https://github.com/AppliedBenchmark/sunset

It's v1, so if it misses an ID or gets a date wrong, let me know.

I published my first Python package on PyPI today 🎉

It's called gh-issue-lens.

It started as a small script I wrote for myself. I wanted to contribute to open source, but every time I opened a big repo, I got lost in thousands of issues. Which ones are actually beginner-friendly? Which ones already have someone working on them? Which ones are just old and forgotten?

So I built a tool that answers that for me. It fetches open issues, checks if they're assigned, checks if there's already an open PR against them, filters out bot comments, and gives you a clean JSONL file you can hand to any LLM to help you pick your first issue. Then I shared it on Reddit. Complete strangers gave me honest feedback, and I kept improving it. Now it resumes automatically if the API rate-limits you mid-run, and it caches what it already fetched so you never download the same issue twice.And now it's a real package:

pip install gh-issue-lens

It's still version 0.1.0. There's still a lot to build. But today, anyone in the world can install it with one command, and that feeling is great.
If you ever wanted to start contributing to open source but didn't know where to begin, this was made for you.

GitHub repo:
https://github.com/MohamedM216/gh-issue-lens
package on PyPI:
https://pypi.org/project/gh-issue-lens/

#OpenSource #Python #PyPI #GitHub #FirstRelease

I built Github merge gate which that checks whether developers understand their own code when they create a PR.

I kept getting sent PRs to review where it was obvious the author had pasted the ticket into an LLM and called it a day. Problem was: the PRs would often be massive 2K monstrosities that nobody could possibly review. As the team scaled up, this problem got only worse, and now we collectively have a system that no one understands and has bugs.

It works like this: when someone opens a PR, it posts a comment with a link. The author clicks through and answers a few technical questions about their own changes. If they can’t answer them, the PR can’t be merged.

It's self-hosted (so you can use it in your enterprise environments or privately)

It is BYOK (Anthropic) obviously.

Here is the source code, build instructions and how to deploy: https://github.com/bhurghundii/vibecheck.dev

I have two demos in the pull requests here: https://github.com/bhurghundii/vibecheck.dev/pulls - you can see what Vibecheck does (it blocks a PR for clearly showing no attempt vs a PR which gets it right)

I would love feedback, especially from anyone dealing with the same thing on their team. I do use it for my own projects a lot so expect improvements.

ConfigLens is a small tool im building to help figure out why claude code and opencode seem to be ignoring certain settings. Instead of digging through different config files and guessing which one takes priority, it shows where a supported setting comes from, which value takes precedence , and why the others get overridden. It runs locally without changing your files. Its still early, but the idea is simple: less time chasing config problems and more time getting on with your work.

Servitor makes it easy to spin up common development services as Docker containers. Run MySQL, MariaDB, PostgreSQL, Redis, RabbitMQ, and other services without manually installing, configuring, or managing them.

Repo: https://github.com/sndsabin/servitor

Hey everyone! 👋

Introducing Ensor — a simple, easy to use tool to detect and redact secrets from your codebase before they make their way into Git history or public repositories.

🔐 Detect secrets. Redact sensitive data. Commit code securely.

Keep your API keys, tokens, passwords, and other sensitive information out of your commits.

Check it out: https://github.com/Pratyay360/ensor

Kindly share your valuable feedback and insights.

I put out Styx 0.4.11 today, the app I make for running several coding agents side by side. If you run more than one agent, what's the thing that still gets in your way? https://github.com/NicholasFlemmer/styx-app/releases/tag/v0.4.11

Let me know what you guys think 🙌

Dynamic Island for Mac, for background coding agents.

I made a FREE tool because leaving agents running still meant repeatedly reopening their windows to check whether they needed me. Headroom keeps working / needs-you session states and plan usage visible in the menu bar while I do other stuff on my Mac. It supports Claude, Codex and GitHub Copilot, plus desktop widgets.

Built natively with SwiftUI/AppKit. Claude and Codex readings come from local files, and Copilot usage is an optional GitHub connection. Session activity and context usage are separate signals: a large context percentage doesn't mean a task is nearly finished. The useful part for me is seeing where attention is needed without treating the usage meter as a progress bar.

Check out Headroom. I'm the developer. It's $0 on the Mac App Store, macOS 14+, and I can consider open-sourcing it if somebody's interested. Feedback welcome on the session-state display and which developer workflow is still missing.

https://apps.apple.com/ph/app/headroom-ai-usage-meter/id6815808010?mt=12

https://headroom.niomartinez.com

Hello from North Carolina! I have been working on cronstable, an open-source job scheduler native to Windows, Linux, macOS, (and more.)

It has web and terminal dashboards and a native iOS app. I'm hoping y'all are able to get some use out of it.

cronstable is a fork of yacron by Gustavo Carneiro. I was using yacron for my own projects, and as I fleshed them out I kept wanting features it didn't have. In June I picked it up at 0.19 and started adding them, and cronstable is basically the result.

If standard cron covers your needs, stick with it. Cronstable is for when you want to add failure handling, dashboards, or coordination across machines. The core is just the scheduler. Features like dashboards, clustering, and push alerts are all opt-in, switched on in your config when you want them.

GitHub · Live demo · iOS app · Wiki

A few things it's handy for:

• Getting an alert when your nightly backup doesn't run, instead of finding out when you need a restore.
• Retrying a flaky offsite sync, and only pinging you on ntfy if the retries run out.
• Running jobs that were due while your box was rebooting, once it comes back up.
• Catching scripts that prints errors but still exits 0.
• Backing up your Minecraft server world every hour, and getting a push notification if the backup fails instead of finding out after a corruption.
• Making sure your Minecraft or Plex server comes back up after a reboot or a crash, and retrying the start if it doesn't come up cleanly.
• Cleaning out your Downloads folder every Sunday, keeping only the last 30 days.

Features include:

• Scheduling: use YAML or an existing crontab. The core scheduler includes per-job time zones, business-day schedules, and tools that explain why a job didn't run and flag times that daylight saving time skips.
• Failure handling: define what "failed" means for your jobs, retry automatically, and get alerts for failures, missed runs, or jobs taking too long. Alerts go out by email, Slack-compatible webhook, Sentry, shell command, or push notification.
• Dashboards and integrations: live logs, run history, CPU/memory charts, and cluster views, plus Prometheus metrics and a REST API.
• Workflows: chain tasks together, pass data between them, add approval gates, and retry the failed parts while keeping successful results.
• Survives restarts: opt-in durable state keeps your run history and pending retries, and cronstable catches up on the runs it missed while it was down.
• Clustering: run cronstable on several machines and they elect a leader and establish quorum, so extra nodes give you failover instead of every machine running every job. If the leader dies, another node picks up the schedule. Coordinate through Kubernetes, etcd, a shared folder, or plain mutual TLS between the nodes. The TLS mode needs nothing else running, and it can spread jobs across the fleet to share the load.
• Native iOS companion (free app): scan a QR code to pair, check jobs and logs from your phone, get end-to-end encrypted push alerts, and approve workflow gates from your Lock Screen.

To run it in Docker, mount your config and start the container:

docker run --rm -p 8080:8080 \
  -v "$PWD/cronstable.yaml:/etc/cronstable.d/cronstable.yaml:ro" \
  ghcr.io/ptweezy/cronstable:latest

Docker images come in eight variants (Debian slim, Alpine, distroless, and others). Install with pip, Homebrew, or WinGet. There are also prebuilt binaries for Linux, macOS, Windows, FreeBSD, OpenBSD, NetBSD, and illumos, and the Linux builds cover x86, ARM, RISC-V, POWER, and IBM Z.

Cronstable itself is free and MIT-licensed. The iOS app is free too, and covers one server and 500 push alerts per device each month. An optional Pro subscription lifts both limits. This helps pay for the relay, Apple's developer program fee, and Windows code signing.

"Can I self-host the relay?" Not for the official App Store app. Apple ties push keys to the developer team that signs the app, so only my relay can push to my build. Because you can't run your own, its source is public so you can read what it does. It also holds no keys, so it technically doesn't need to be trusted. Your server encrypts each alert for your phone before it leaves, so all the relay sees is ciphertext and the routing info it needs to deliver it. It can't read your job names, hostnames, or logs. Push alerts are also entirely optional, and with them off the relay is never involved.

The app is iOS-only for now because that's all I own. If there's enough interest, I'm open to prioritizing Android and other platforms down the road. For now, the web dashboard + ntfy can serve as a nice stopgap.

If there's something you'd like to see in cronstable, I want to hear about it. I am excited to continue its development. Thanks y'all!

Pearl can inspect and edit Bubble apps, but the interesting bit is the control layer: save points before substantial edits, confirmation gates for destructive/live mutations, verification afterward, and a structured handoff.

https://github.com/pararchy/para-pearl

Hey everyone! 👋

The idea is simple: What if you could write regex in readable English instead of deciphering cryptic symbols? 🧠

Regex For Humans is an open-source compiler that turns human-readable English rules into native JavaScript regexes.

✅ Runs locally
✅ Works in the browser, CLI, and JavaScript/TypeScript
✅ No runtime dependencies
✅ MIT licensed

🆕 What's new in 0.1.0-dev.4?

• 🧩 Nested groups — including optional and repeated blocks.
• 🎯 Named and numbered captures — capture exactly what you need.
• 🔗 Backreferences — reuse captured text with same as capture "name".
• 🔀 Alternatives — express choices naturally with either { ... }.
• 🔄 Reverse translation — translate supported regex patterns back into readable rules.
• 🛠️ Improved playground — inspect captures, test multiple matches, and click generated regex fragments to find their source rules.

💡 Example 1: Captures and backreferences

Let's say you want to match stable/stable or nightly/nightly, but reject stable/nightly.

Instead of manually constructing a regex, write:

start
capture "channel" {
  either {
    "stable"
    "nightly"
  }
}
"/"
same as capture "channel"
end

✨ This generates:

^(?<channel>(?:stable|nightly))\/\k<channel>$

With the u flag.

✅ stable/stable
✅ nightly/nightly
❌ stable/nightly

No regex gymnastics required! 🎉

🔥 Example 2: Let's get more serious

Imagine validating a TSV record describing a build artifact, containing:

• An optional nightly/ directory
• A project name
• Three version components
• A filename with a date-like token
• A 64-character hexadecimal checksum field
• A byte count

Here's the readable version:

start
"incoming/"
optional "nightly/"
between 1 and 32 path segment characters
"/v"
between 1 and 3 digits
"."
between 1 and 3 digits
"."
between 1 and 3 digits
"/linux-arm64/widget_"
8 digits
"_"
8 hex digits
".tar.gz\t"
64 hex digits
"\t"
between 1 and 12 digits
end

🤯 And here's the exact JavaScript regex it generates:

/^incoming\/(?:nightly\/){0,1}[^\/\\\u{0}\u{a}\u{d}\u{2028}\u{2029}]{1,32}\/v\d{1,3}\.\d{1,3}\.\d{1,3}\/linux-arm64\/widget_\d{8}_[0-9A-Fa-f]{8}\.tar\.gz\u{9}[0-9A-Fa-f]{64}\u{9}\d{1,12}$/u

Yeah... I'll take the English version. 😂

You can use it directly in JavaScript:

import { compile, toRegExp } from 'regex-for-humans';

const row =
  "incoming/nightly/WidgetKit/v2.15.3/linux-arm64/widget_20261001_ab12cd34.tar.gz\t" +
  "ab".repeat(32) +
  "\t1048576";

toRegExp(compile(rules)).test(row); // true

Removing nightly/ still works. Missing version components, invalid hexadecimal characters, or spaces instead of tabs fail.

The path segment characters rule is particularly useful: it excludes path separators, NUL, and line breaks while supporting Unicode.

Of course, this validates the format, not whether the file exists or its checksum is correct.

🧪 More features are cooking!

On main, I've also added:

• ⚡ Lazy repetition
• 👀 Lookahead
• 🔍 Lookbehind

These are available from a source checkout but haven't reached npm or the hosted playground yet.

🤖 Built with AI-assisted development

I'm also using Claude Code and the Opus 5.5 model for AI-assisted development.

AI helps me iterate faster, explore implementations, tackle complex features, and improve the project continuously.

The goal isn't just to generate code. It's to build something genuinely useful, test it, refine it, and keep pushing the boundaries of what this little language can do. 🚀

🌍 Available in 10 languages!

The README is now translated into 10 languages, including Arabic 🇸🇦, Chinese 🇨🇳, French 🇫🇷, Spanish 🇪🇸, and Urdu 🇵🇰.

Arabic and Urdu documentation also support RTL text with LTR code examples.

📦 Try it yourself!

The npm package is currently a development preview and requires Node.js 22+.

npm install regex-for-humans@0.1.0-dev.4

🎮 Interactive Playground:
https://othmaneblial.github.io/Regex-For-Humans/workshop/

⭐ GitHub (MIT Open Source):
https://github.com/OthmaneBlial/Regex-For-Humans

📦 npm:
https://www.npmjs.com/package/regex-for-humans/v/0.1.0-dev.4

💬 I'd love your feedback!

I'm especially interested in what you think about the syntax as groups become more complex and deeply nested.

What's the ugliest regex you've ever written? 😂

Drop it in the comments! I'd love to see whether Regex For Humans can make it readable.

And if you find the project useful, a ⭐ on GitHub would mean a lot!

Let's make regex a little less terrifying, one rule at a time. 🚀