u/Vivid-Strength6137 — reddlx

Thinking about building a carrier verification tool — what's your take?

I've been thinking about a concept called LoadVetter — a tool that would let a broker check a carrier in under 60 seconds. Enter an MC number, get a risk assessment from FMCSA data plus fraud signals (VoIP phone flag, authority age, recent FMCSA changes, etc.), plus COI OCR and carrier self-onboarding.

I'm NOT building anything yet — just in the idea phase and trying to understand if this is even a real problem worth solving.

A few questions for those who've been in the industry:

How much time do you actually spend verifying a single carrier?
What's the most annoying part of the process?
If a tool like this existed and was reasonably priced, would you use it or stick with what you have now?

Not selling anything, just trying to learn. Appreciate any thoughts.

reddit.com

u/Vivid-Strength6137 — 3 days ago

▲ 6 r/npm

1.4k weekly npm downloads but almost no feedback — is this normal or mostly bots?

I recently published a small CLI tool on npm. It is getting around 1.4k weekly downloads, but I’m getting almost no feedback, issues, comments, or discussions.

I’m trying to understand how to interpret this.

For npm maintainers:

- Is it normal to see weekly downloads without any user feedback?
- Can a big part of this be bots, mirrors, security scanners, CI, or repeated `npx` runs?
- Do `npx` runs count as downloads?
- Is there any way to know whether downloads are real users or automated traffic?
- What kind of download-to-feedback ratio is normal for a new package?

I’m not trying to claim traction from downloads alone. I just want to understand whether this is a meaningful signal or mostly noise.

reddit.com

u/Vivid-Strength6137 — 1 month ago

▲ 1 r/softwaretesting+1 crossposts

I built an OSS tool to catch weak AI-written tests using mutation testing

I built a small open-source tool for a problem I keep seeing with AI coding agents:

AI-written tests often pass, but they do not always protect real behavior.

The tool is called Tautest.

It runs StrykerJS mutation testing on changed source lines, finds surviving mutants, and generates an AI-ready fix prompt for Claude Code, Cursor, Codex, or a human reviewer.

The idea is not:

“AI wrote tests, so trust them.”

It is:

“AI wrote tests, now mutate the changed code and see whether those tests actually fail.”

Example from the demo:

age greater than or equal to 65 becomes age greater than 65

The regular tests passed, but the mutant survived because the exact boundary at 65 was not tested.

Then Tautest writes a prompt with rules like:

- do not change production code

- only add or strengthen tests

- the new test must pass on original code

- the new test must fail on the mutant

GitHub:

https://github.com/canblmz1/tautest

npm package:

tautest

It is MIT licensed, deterministic, and does not call any LLM API itself. It just produces the prompt and report.

I would appreciate feedback from people using AI coding agents in real repos:

- would you run something like this locally?

- would you add it to PR checks?

- is the AI fix prompt workflow useful or too much friction?

reddit.com

u/Vivid-Strength6137 — 2 months ago

▲ 1 r/coolgithubprojects

dbsnap - save and restore local PostgreSQL/SQLite dev database states

I built `dbsnap`, an open-source CLI for saving and restoring local development database states.

GitHub:

https://github.com/canblmz1/dbsnap

It is meant for workflows where you keep rebuilding the same local database state while developing or testing:

- run migrations

- seed the database

- click through the app until the UI is in the right state

- break the local DB while testing something

- repeat

With `dbsnap`, you can do:

```bash

npm install -D u/canblmz1/dbsnap

npx dbsnap save dev-ready

# change or break your local database

npx dbsnap restore dev-ready --yes

```

Current support:

- SQLite

- PostgreSQL

- Prisma / Drizzle workflows

- Vitest / Playwright setup flows

- Docker fallback for local PostgreSQL tooling

- snapshot verification

- snapshot pruning

- safety checks for remote/production-looking database URLs

It is intentionally **not** a production backup tool. It is for disposable local development databases only.

I tested it on a cloned Prisma SQLite example project and added a terminal demo GIF in the README.

I’d love feedback from people who use local databases in development or write test setup flows.

u/Vivid-Strength6137 — 2 months ago

▲ 2 r/SideProject

I got tired of rebuilding local DB state, so I made a tiny snapshot CLI

Hey everyone,

I built a small dev tool called `dbsnap` because I kept running into the same annoying workflow:

1. Run migrations

2. Seed the database

3. Click through the app until the UI is in the right state

4. Break something while developing or testing

5. Repeat everything again

`dbsnap` lets you save and restore local development database states from the CLI.

It currently supports:

- SQLite

- PostgreSQL

- Prisma / Drizzle style workflows

- Vitest / Playwright setup flows

- Docker fallback for local PostgreSQL tooling

- `npx` / npm package usage

Package: `@canblmz1/dbsnap`

npm:

https://www.npmjs.com/package/@canblmz1/dbsnap

Example:

```bash

npm install -D '@canblmz1/dbsnap

npx dbsnap save dev-ready

# mess up your local database while developing

npx dbsnap restore dev-ready --yes

```

This is intentionally **not** a production backup tool. It is only meant for disposable local development databases.

I also added safety checks so it tries to avoid accidentally running against remote or production-looking database URLs.

GitHub/demo:

https://github.com/canblmz1/dbsnap

I’m looking for feedback from people who deal with local DB reset pain, especially Prisma, Drizzle, Vitest, Playwright, PostgreSQL, or SQLite users.

Would this fit into your dev workflow, or is there a better way you already handle this?

u/Vivid-Strength6137 — 2 months ago

▲ 3 r/npm+2 crossposts

I built dbsnap, an npm CLI to snapshot and restore local PostgreSQL/SQLite dev databases

Hey, I built dbsnap because I kept losing time re-running migrations, seeds, and UI setup flows just to get my local dev database back to a known state.

It is a small npm CLI for local development databases:

- PostgreSQL and SQLite

- Prisma / Drizzle workflows

- Vitest / Playwright setup flows

- npm/npx friendly

- local restore safety checks

- not a production backup tool

Install:

npm install -D u/canblmz1/dbsnap

npx dbsnap save dev-ready

npx dbsnap restore dev-ready

Repo/demo:

https://github.com/canblmz1/dbsnap

I’d love feedback from people who deal with annoying local DB reset workflows.

u/Vivid-Strength6137 — 2 months ago

▲ 2 r/IMadeThis

I kept copy-pasting stuff like "kral login token refresh bozuldu başka yeri bozma" into ChatGPT and getting garbage back.

Not because ChatGPT is dumb. My prompts were just trash. No context, no scope, no guardrails.

So I built PromptFix — a tiny local tool that rewrites your rough coding requests into something actually useful.

You select text anywhere, hit a hotkey, and it replaces your lazy prompt with a structured one.

Before:

```

After:

```

Investigate and fix the login token refresh issue with minimal, targeted changes. Inspect the existing auth flow first, avoid unrelated refactors or config/secrets changes, run relevant tests if available, and summarize the root cause, fix, and verification steps.

```

I added a couple things I personally wanted:

- Works 100% locally (no SaaS, no accounts)

- Sub-second with Groq, works offline with Ollama

- Built-in evaluation: 40 tests to check if outputs are actually good

- Discord-like chat with snippets and slash commands

- Understands Turkish slang because that's what I write in

Tech stack is boring on purpose: Python + vanilla JS. No React, no Docker, no cloud functions.

MIT licensed, 174 tests, open source: https://github.com/canblmz1/promptfix

If you try it and it breaks (it will), tell me what broke. I actually fix stuff.

u/Vivid-Strength6137 — 2 months ago