floze-the-genius
SAM lint summary diagnostics with focused evidence, fixtures, and a clear next step.
View profileCOMMUNITY HALL OF FAME
A deployment tool becomes trustworthy in public: one real failure, one careful fixture, one review that catches the edge case. This is a thank-you wall for the people who have helped make the next check more useful.
THE FIRST WAVE
These are the contributors currently named in the project record. The descriptions focus on what they made better, not on a leaderboard.
SAM lint summary diagnostics with focused evidence, fixtures, and a clear next step.
View profileDiagnostic rules, CI, fixtures, and contributor tooling that made the project easier to extend.
View profileLambda package-size diagnostics that turn a confusing deployment ceiling into a focused next check.
View profileDeprecated Lambda-runtime diagnostics that help teams see the migration path before retrying a deploy.
View profileLambda deployment diagnostics that make a noisy failure easier to investigate locally.
View profileNear-match test coverage that protects the boundary between a useful signal and a false positive.
View profileNon-ASCII property validation diagnostics that catch invisible template failures before they cost a deploy.
View profileGit history also credits Harshil for Lambda deployment package-size diagnostics. Their commit author record is intentionally unlinked because no public GitHub profile is attached to it.
YOUR TURN
You do not need to know the whole codebase. A sanitized failure report, a docs correction, a fixture, or a small diagnostic rule is a complete contribution. Maintainers will help you find the right first step.
The wall is human-maintained and never a requirement for contribution. Ask for a correction or open a small PR through the contributor guide.