오늘 스토리에서 기준을 통과한 아이디어가 없습니다. 약한 아이디어를 싣느니 싣지 않는 편이 낫습니다.
검토한 스토리
25
정독
3
제안된 아이디어
6
살아남음
0/6
6.0점 기준선을 넘은 아이디어가 없습니다.
탈락 · 6 · 6.0점 기준선 아래
| 5.1 | AI red-team service for language runtimes | The named buyers are nearly nonexistent as paying customers — language foundations are cash-poor and get Google's Big Sleep/OSS-Fuzz for free — while clouds do this in-house, leaving a handful of contracts against XBOW and ZeroPath. |
| 4.9 | Package mirror with enforced release cooldown | Artifact repositories already sit exactly here and a package-age policy is a trivially added feature — Sonatype Repository Firewall and JFrog Curation already quarantine components by policy, and uv ships exclude-newer natively for free. |
| 4.8 | PHP estate exposure scanner and patch verifier | Tenable, Qualys and Wiz already inventory runtimes and flag engine-level CVEs with authenticated checks, and 'did the patch work' verification is a feature they add, not a company — the budget owner already pays them. |
| 4.5 | Artifact-to-source diff monitor for package registries | The whole business rests on rebuild-and-diff being reliable at registry scale, but almost no PyPI/npm packages are reproducible, so false positives drown the signal — and the entire evidence base is one LiteLLM incident. |
| 4.4 | One-command sealed sandboxes for installs and agents | Free tools already do this (bubblewrap, firejail, devcontainers) and the agent vendors themselves are baking in sandboxing — Anthropic open-sourced its sandbox runtime for Claude Code — so the $10-20/seat buyer will just use what ships with their agent. |
| 4.2 | Multi-party vulnerability disclosure coordination tool | CERT/CC's VINCE already exists, is free, and is purpose-built for multi-party coordinated disclosure with embargo timelines, and foundations/PSIRTs will not pay $200-800/mo for a parallel system of record. |