Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
Scan pending.
Live mentions badge
Show how many posts mention your project in the last 30 days.
Live mentions · last 30 days
Mentions
@mitch_petel A remote env is already a good security boundary to begin with. BTW that remote can also just run in a local docker container (see my boxdown CLI project: lirantal/boxdown) - the point is isolation from your main host OS What dev experience sucked for you in particular?
@bentlegen Ben are you stealing my OSS?? Boxdown lirantal/boxdown
@chr33s Hah, nice Chris. I guess we're all just vibe coding our isolated environments, aren't we? :-) Speaking for myself - I've done the same to build out boxdown: lirantal/boxdown
@phretor @trailofbits Here's a similar project, from just good ol' me :-) It's called boxdown: lirantal/boxdown
@karlclement I've been working with coding agents to run them inside VMs (well, containers) on my mac work laptop since forever (due to the security paranoia) It started with simple scripted workflow and then I built boxdown (lirantal/boxdown) to autoconfigure all of that for me. Codex or Claude install their server-side agents on the container and then connect to it from the app via a remote SSH connection that boxdown also sets up However, I'm going to go try AmpCode and Orbs now Karl (thanks for setting me up!). I do believe (and predict) the future is remote development.