Shamefile

v0.1.0 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 1mo Developer Productivity

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

cli code-quality code-review developer-tools linter noqa

+4 more

pre-commit rust static-analysis technical-debt

Summary

AI summary

Introduces enforcement of documented ownership and rationale for all linter suppressions.

Full changelog

shamefile v0.1.0

First stable release. shamefile turns linter suppressions (# noqa, // eslint-disable-next-line, # type: ignore, # nosec, etc.) from silent technical debt into reviewable, documented decisions — every suppression must come with an owner and a why, enforced in CI via `shame me

Breaking Changes

All linter suppression directives (e.g., `# noqa`, `// eslint-disable-next-line`, `# type: ignore`, `# nosec`) now require an associated owner and a documented 'why' field; failing to provide these causes CI failures.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track Shamefile

Get notified when new releases ship.

About Shamefile

All releases →