C — Moderate risk signals Graded October 18, 2026Several concerns worth a closer look before you install.Based on public adoption and transparency signals as of Oct 18, 2026. Our opinion, not a code audit or security guarantee.
AI agent skill · Developer tools, Files & documents
kotlin-footguns
Battle-tested agent skills mapping the footguns of Kotlin, Compose Multiplatform and the desktop JVM — mined from a production music app, not from documentation.
Bottom line: This is a low-risk reference document since it's not executable code, but teams should verify each issue applies to their specific Kotlin version and framework versions before relying on it.
- Popularity score
- 36/100
- Rank
- #432 of 500
- GitHub stars
- 1.4k
What it does
A collection of common mistakes and gotchas (called "footguns") in the Kotlin programming language, Compose Multiplatform framework, and desktop Java applications. It documents real issues found in a production music app to help developers avoid similar problems.
Who it’s for
Kotlin developers building desktop or multiplatform apps, especially those using Compose. Teams wanting to learn from real production issues rather than just reading documentation.
Copy-paste setup
Check these steps against the project’s own instructions before running anything.
Follow the project's README at https://github.com/maxrave-dev/kotlin-footguns (opens external site) for documentation and examples. This is a reference resource, not an installable package.
Risks
- Educational content only: This is documentation, not executable code, so it cannot directly access systems or data itself
- Outdated information risk: Kotlin and frameworks evolve; listed issues may be fixed in newer versions
- False confidence: Using this as the only reference could miss issues not covered or create gaps in understanding
- Third-party links: Any external links in the repository could point to unvetted sources
- Context-dependent mistakes: Issues described may not apply to all projects or may need adjustment for specific use cases
How to stay secure
Least-privilege permissions
- Review issues carefully before applying fixes to production code
- Test changes in a staging environment first
Network isolation
- This resource is offline once cloned; no continuous network access needed
- Be cautious if following any links to external examples
Monitoring
- Track which footguns affect your codebase and monitor for regressions
- Keep your Kotlin and Compose versions updated and re-check compatibility
Red flags to watch for
- Claims that all listed issues apply to your specific version (test first)
- External links promising quick fixes without explanation
- Treating this as a security guide instead of a development reference
Alternatives
- Kotlin official documentation and release notes: Direct guidance from JetBrains on language features and breaking changes
- Compose Multiplatform best practices guide: Official resource for Compose-specific patterns and warnings
- Arrow or other Kotlin libraries' documentation: Additional functional programming patterns to avoid common errors