SAM Doctor

COMMUNITY HALL OF FAME

The people who made SAM Doctor sharper.

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.

7named community contributors
90documented diagnostics to improve
GitHubcurrent issue queue and discussions

THE FIRST WAVE

People who shipped changes

These are the contributors currently named in the project record. The descriptions focus on what they made better, not on a leaderboard.

02rules + tooling

waterlemonnn

Diagnostic rules, CI, fixtures, and contributor tooling that made the project easier to extend.

View profile
03Lambda

pui1ya

Lambda package-size diagnostics that turn a confusing deployment ceiling into a focused next check.

View profile
04runtime support

alloutflo

Deprecated Lambda-runtime diagnostics that help teams see the migration path before retrying a deploy.

View profile
05deployment rules

rasmalai25

Lambda deployment diagnostics that make a noisy failure easier to investigate locally.

View profile
07template validation

agu2347

Non-ASCII property validation diagnostics that catch invisible template failures before they cost a deploy.

View profile

Git 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

There is room for the next name.

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.