Show HN: Repogen – a static site generator for package repositories
Show HN (score: 17)Description
Package repositories don't need to be complicated. They're just static files: metadata indexes and the packages themselves. Yet somehow hosting your own feels like you need dedicated infrastructure and deep knowledge of obscure tooling.
repogen is an SSG for package repos. Point it at your .deb/.rpm/.apk files, it generates the static structure, you upload to S3 or any web host. Done. $0.02/month to host packages for your whole team.
It supports Debian, RPM, Alpine, Pacman, and Homebrew. Has incremental mode for updating repos without redownloading everything. Handles signing. Very alpha, but it works. Would love to get feedback!
More from Show
Show HN: Spice Cayenne – SQL acceleration built on Vortex
Show HN: Spice Cayenne – SQL acceleration built on Vortex Hi HN, we’re Luke and Phillip, and we’re building Spice.ai OSS - a lightweight, portable data and AI engine and powered by Apache DataFusion & Ballista for SQL query, hybrid-search, and LLM-inference across disaggregated-storage used by enterprises like Barracuda Networks and Twilio.<p>We first introduced Spice [1] on HN in 2021 and re-launched it on HN [2] in 2024 re-built from the ground up in Rust.<p>Spice includes the concept of a Data Accelerator [3], which is a way to materialize data from disparate sources, such as other databases, in embedded databases like SQLite and DuckDB.<p>Today we’re excited to announce a new Ducklake-inspired Data Accelerator built on Vortex [3], a highly performant, extensible columnar data format that claims 100x faster random access, 10-20x faster scans, 5x faster writes with a similar compression ratio vs. Apache Parquet.<p>In our tests with Spice, Vortex performs faster than DuckDB with a third of the memory usage, and is much more scalable (multi-file). For real-world deployments, we see the DuckDB Data Accelerator often capping out around 1TB, but Spice Cayenne can do Petabyte-scale.<p>You can read about it at <a href="https://spice.ai/blog" rel="nofollow">https://spice.ai/blog</a> and in the Spice OSS release notes [4].<p>This is just the first version, and we’d love to get your feedback!<p>GitHub: <a href="https://github.com/spiceai/spiceai" rel="nofollow">https://github.com/spiceai/spiceai</a><p>[1] <a href="https://news.ycombinator.com/item?id=28448887">https://news.ycombinator.com/item?id=28448887</a> [2] <a href="https://news.ycombinator.com/item?id=39854584">https://news.ycombinator.com/item?id=39854584</a> [3] <a href="https://github.com/vortex-data/vortex" rel="nofollow">https://github.com/vortex-data/vortex</a> [4] <a href="https://spiceai.org/blog/releases/v1.9.0" rel="nofollow">https://spiceai.org/blog/releases/v1.9.0</a>
Show HN: Daily install trends of AI coding extensions in VS Code
Show HN: Daily install trends of AI coding extensions in VS Code For the past 4 years, I've been tracking the install counts of AI coding extensions in the Visual Studio Code marketplace (GitHub Copilot, Claude Code, OpenAI Codex, etc.)<p>Today, I built an interactive dashboard that lets you see daily install counts for any of them over time.<p>The chart shows GitHub Copilot by default, and you can overlay or swap in any of the other 20+ tools to compare. You can also see important dates in each tool's history (pricing changes, major releases, etc.) and how daily installs changed around those dates.<p>Important caveats:<p>1) This only tracks VS Code extension installs, not CLI usage or other IDEs like JetBrains.<p>2) Cursor isn't included since it's a standalone editor (VS Code fork), not a marketplace extension. I added a second chart showing Cursor discussion forum activity as a proxy for its growth.<p>Obviously not apples to apples, but felt I needed to measure Cursor's growth somehow.<p>3) This tracks daily installs per day, NOT total installs. Otherwise the charts would be boring and always go to the top and right.<p>4) The dashboard was coded using an AI coding assistant too. I used regular Claude :)
Show HN: I built an open-source AI data layer that connects any LLM to any data
Show HN: I built an open-source AI data layer that connects any LLM to any data Excited to share a project I’ve been building for months! Would love to receive honest feedback :)<p>My motivation: AI is clearly going to be the interface for data. But earlier attempts (text-to-SQL, etc.) fell short — they treated it like magic. The space has matured: teams now realize that AI + data needs structure, context, and rules. So I built a product to help teams deliver “chat with data” solutions fast with full control and observability (agent tracing, quality scores, etc) — am I wrong?<p>The product allows you to connect any LLM to any data source with centralized context (instructions, dbt, code, AGENTS.md, Tableau) and governance. Users can chat with their data to build charts, dashboards, and scheduled reports — all via an agentic, observable loop. With slack integration as well!<p>* Centralize context management: instructions + external sources (dbt, Tableau, code, AGENTS.md), and self-learning<p>* Agentic workflows (ReAct loops): reasoning, tool use, reflection<p>* Generate visuals, dashboards, scheduled reports via chat/commands<p>* Quality, accuracy, and performance scoring (llm judges) to ensure reliability<p>* Advanced access & governance: RBAC, SSO/OIDC, audit logs, rule enforcement<p>* Deploy in your environment (Docker, Kubernetes, VPC) — full control over infrastructure<p>GitHub: github.com/bagofwords1/bagofwords<p>Docs / architecture / quickstart: docs.bagofwords.com
Show HN: Prism – Let browser agents access any app
Show HN: Prism – Let browser agents access any app Hey HN, We’re Alex, Land, and Rajit. We’re building Prism (prismai.sh), a tool that helps browser agents authenticate onto websites with user credentials. Developers pass in credentials, Prism logs into a website on their behalf, and hands them back the cookies so they have an authenticated session. Here’s an example of how developers can use Prism to complete username/password flows (<a href="https://youtu.be/SEtVUnWnxuE" rel="nofollow">https://youtu.be/SEtVUnWnxuE</a>), and here’s an example of how developers can use Prism to complete login flows that require an OTP code (<a href="https://youtu.be/fe9w9PvrwH0" rel="nofollow">https://youtu.be/fe9w9PvrwH0</a>).<p>We spoke to browser agent developers and saw people copying and pasting credentials and even credit card numbers directly into model system prompts. We were surprised that there wasn’t a better way to give agents access to websites on a human’s behalf. Moreover, we noticed that every company had to build infrastructure to manage OTP, TOTP, and MFA and that auth remained a significant hurdle in agent reliability. We wondered if this was a boring part of the problem of building web automations that someone could automate away.<p>We started working with Casco, an autonomous security testing company, to enable their agent to access customer sites. Before a pentest, Casco makes a request to Prism’s API specifying test user credentials, a domain, and a login method. For example, give me an authenticated session for the account rajit@prismai.sh for OpenAI via OTP code over email. Our agent logs in on their behalf (without exposing credentials to a model), and we download the cookies and send them back in the response.<p>To maintain speed and reliability, we use playwright in most cases to login (which gives us speed), and we fallback to AI on failure (which gives us reliability). We have a number of websites we support out of the box and add new scripts as the number of websites we need to support grows. We are working on a way for the agent to update the existing playwright script on failure, so our scripts always stay up to date.<p>To try our api, you can use our API playground docs.prismai.sh/api-reference/endpoint/login to sign into x.com with the following API key: pk_54abb1cd0a637eb973ed690416e71a953e98f2ea839cf16529bbfa41a41bc016 .<p>We’d love to learn more about how other developers give agents access to their accounts. We look forward to everyone’s feedback and comments.
No other tools from this source yet.