News for hackers. Stuff that matters.

fkjadoon94

Re:Taking down Next.js servers for 0.0001 cents a pop on Thursday November 27, 2025 @10:12AM (#46069953)
Clever! Wonder if the agent utilized some sort of fuzzing during its exploration loop, and what size of test space.
Re:Show HN: Muscle-Mem, a behavior cache for AI agents on Thursday May 15, 2025 @08:38AM (#43994379)
Excited to check it out!

Erik is a true hustler and ML infra builder at the core, not in this for the antics. Known him since the Booste days.

Re:The Pain That Is GitHub Actions on Friday March 21, 2025 @09:43PM (#43442533)
The integration basically wraps *jibril - a single binary linux edr which allows for detection and enforcement in the runner

https://jibril.sh

Re:The Pain That Is GitHub Actions on Friday March 21, 2025 @09:35PM (#43442494)
Yes, its a one step integration into your workflow file, typically before the steps you want to monitor eg. build, test if you don't want to see everything happening in your runner host. It has worked pretty well with ubuntu-latest and stock Linux runners from GH out of the box.

Show HN: Proactive Security Monitoring for GitHub Actions Workflows

Hey HN, it's Farrukh and Umar. We're building listen.dev–a tool for proactive security monitoring in GitHub Actions to secure software releases from supply chain threats.Why we built this:As friends and collaborators for over a decade, we've been working on various startup ideas in dev tools and infrastructure. In 2017, while building an ML ops toolkit on Kubernetes, we got hacked. During a...

( Read More... | 7 comments | 25 points | on HN )
I believe the goal here isn't to replace Vault, but offer a developer focused solution for environment variable management. While Vault can be used to store env variables, its more geared towards managing infra secrets for the ops/sre persona.
Please see the response on your other comment regarding the Vault comparison.
Very valid point - the main problem to solve here isn't storage and encryption. We think the clouds do a great job for that, hence our self-hosted approach.

It’s important to note that the goal here is not to replace Vault. Vault pioneered a lot of best practices in this space, which we build on top of. The gap we want to fill is of complexity and developer-experience, while playing well with existing tools, as stated.

Re: identity – it’s on our immediate roadmap to integrate with identity providers (similar to Vault). We offer a similar model of pluggable secrets backends inspired by Vault (currently supporting DB’s such as Postgres and Mongo). If you want to use your existing SSO provider, our private enterprise beta comes with WorkOS integration. Please reach out at [email protected] if you’re interested, and we’d love to talk more about your specific needs!

Managing secrets is critical in this day and age for individuals and organizations of all kinds and sizes. Many developers currently find it painful to manage their app configurations and secrets, and this pain grows with stack complexity and team size. This makes building and deploying manual, time-consuming and insecure.

Today there are great solutions in this space, however, from our personal experience as developers, we have felt that existing solutions are either:

1) Too complex to set up and operate for the everyday developer

2) Tied to cloud-providers and don’t work well cross-platform

3) Pure SaaS solutions don’t play well with trust and reliability

Because of this, engineers end up writing custom wrappers around existing tools to solve developer experience and integrations with their stack.

Garnet is a developer-focused, open-source secrets manager which can be easily self-hosted on your own infrastructure. We aim to provide a single source of truth for configs and secrets across your tools, apps, environments and teams while delivering a great developer-experience through features like rich audit logs and versioning, granular access controls, notifications and native integrations with existing secrets and config management systems.

Garnet wants to solve this problem from a developer-first point of view, and we want to work with the community to elevate configurations as a first-class citizen in a developer’s workflow.

We’re actively looking for feedback and contributions! Please star and check out our GitHub repo to read more on what we’re building: https://github.com/garnet-labs/garnet-oss

Definitely a problem -- excited to see a solution in this space!
How do you compare with LayerCI (https://layerci.com/)?
Re:Apple Edge Cache on Friday February 14, 2020 @03:34PM (#22330131)
Copyright © 2019 Apple Inc.