#untrustedcode
Live, measured metrics for the hashtag #untrustedcode from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #untrustedcode
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 22:14 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 22:14 UTCNo related tags with measured usage found for #untrustedcode.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 22:14 UTCEverything below is measured over the latest 2 public posts (spanning ~9010 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
How we run untrusted customer code at scale Nango는 고객이 작성한 신뢰할 수 없는 코드를 대규모로 안전하게 실행하기 위해 다양한 런타임 아키텍처를 발전시켜왔다. 초기 Node.js vm2 샌드박스는 보안 취약점으로 인해 프로세스 분리된 러너 모델로 전환했고, 이후 AWS Lambda를 도입해 하드웨어 수준의 격리와 확장성을 확보했다. Lambda 환경에서 고객별 함수 분리를 통해 테넌트
🚀 Announcing "Microsandbox": the revolutionary technology that combines the inefficiency of virtual machines with the false security of containers! 🎉 Finally, a platform that lets you run untrusted code in a way that feels just as clunky
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/untrustedcode