Rejected repos
58 repos that won't work — and exactly why. The rejection analysis is often more useful than the qualified list.
No LICENSE file present in the repository
No LICENSE file, so the code cannot be legally used in a commercial product.
No LICENSE file in the repository, making commercial use unsafe despite README text
No LICENSE file — cannot legally use or commercialize the code.
No LICENSE file—cannot legally reuse the content in a commercial product.
Crowded space with dominant free alternatives (React Hook Form, Formik) offering broader features and modern React patterns, leaving little to monetize.
Clear overlap with existing free and paid tools (go mod why, golangci-lint depguard, Sourcegraph, CodeSee) that already solve dependency tracing/visualization and PR feedback, reducing willingness to pay for a narrowly-scoped Go-only tool.
Well-served market: PortfolioVisualizer, Morningstar, and Nitrogen (Riskalyze) already provide similar or richer return-distribution education and planning tools.
It’s an on‑device iOS SDK, not a service, so turning it into a revenue‑generating web product would require building a new cloud pairing service, dashboard, and distribution model beyond the repo’s scope.
It’s a narrow utility library overlapping with Swift’s built-in interpolation/FormatStyle and common formatters, offering little differentiation for a paid product.