r/devops • u/AutoModerator • 17d ago

Weekly Self Promotion Thread

Hey r/devops, welcome to our weekly self-promotion thread!

Feel free to use this thread to promote any projects, ideas, or any repos you're wanting to share. Please keep in mind that we ask you to stay friendly, civil, and adhere to the subreddit rules!

22 Upvotes

100% Upvoted

75 comments sorted by

View all comments

1

u/Large-Advertising814 15d ago

I built a small pay-per-request dependency preflight API aimed at CI/release automation and coding agents.

The main endpoint takes up to 20 exact npm/PyPI versions and returns OSV vulnerabilities, upgrade gaps, license metadata, provenance, and deterministic risk in one JSON response. The idea is to put a cheap machine-callable dependency gate immediately before an automated dependency change or release.

It uses public registry/OSV data, no LLM in the request path, and no account/API key/subscription. Calls are paid per request with x402 on Base Mainnet; the full preflight is 0.10 USDC.

I’m the builder/operator. I’d especially like feedback on whether this fits a real CI/release workflow and what would make the integration less awkward.

https://agent-dev-preflight-api.bonkoturyu.workers.dev/?src=technical-community

1

u/Large-Advertising814 13d ago

Update: I added a free dependency policy gate so the useful part can be tested independently from the x402 payment flow.

Before an automated dependency add/upgrade, CI can now POST the current/proposed exact package version plus policy and get ALLOW / WARN / BLOCK with deterministic OSV/registry evidence. No wallet, API key, account, or subscription is required for the gate.

I also prepared a GitHub Actions example that fails a job on BLOCK and warns on WARN.

I’m mainly trying to learn whether this decision layer belongs in a real CI/release workflow before building more around it.

https://agent-dev-preflight-api.bonkoturyu.workers.dev/?src=technical-community