SlopScore
00 crowd

perfectionist (github.com/KSXGitHub/perfectionist)

Additional linting rules for Rust projects
Rust · ★ 13 · 2 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 2 hours ago by KSXGitHub · last checked 32 minutes ago · demo
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-11: A set of extra Dylint lint rules for Rust projects; its FAQ admits "This code base is almost entirely AI-generated. Or in other words, vibe-coded.". 13 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as KSXGitHub. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
Additional linting rules for Rust projects
website
https://ksxgithub.github.io/perfectionist/
topics
code-qualitydylintlinterquality-controlruststatic-analysis
created
2026-05-09 · pushed 48 minutes ago · 321 commits · 5 contributors
languages
Rust 95%CSS 2%JavaScript 2%Shell 1%Just 0%
paperwork
licensereadme 42% health
dependencies
⚠ 6 of 208 deps have known advisories · OSV.dev, checked 32 minutes ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
cssjavascriptjustrustshell
topic (detected)
code-qualitydylintlinterquality-controlruststatic-analysis
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: A set of extra Dylint lint rules for Rust projects; its FAQ admits "This code base is almost entirely AI-generated. Or in other words, vibe-coded.". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README (read the rest on GitHub)

perfectionist

Additional linting rules for Rust projects.

Rules

See the homepage or the rules/ directory for all the rules implemented so far.

See planned-rules/ for all the rules not yet implemented.

Usage

Install Dylint, then add perfectionist to your workspace's dylint.toml:

[workspace.metadata.dylint]
libraries = [
    { git = "https://github.com/KSXGitHub/perfectionist" },
]

Run the lints:

cargo dylint --all -- --all-targets

Controlling rules

Each lint registers under the perfectionist tool namespace. See CONTROLLING_RULES.md for how to change a rule's level per call site or project-wide, and how to enable or disable rules globally.

Configuration

dylint.toml accepts a crate-wide [perfectionist] table and per-rule ["perfectionist::<rule>"] tables. See CONFIGURATION.md for the full schema.

Development

Prerequisites:

cargo-dylint and dylint-link are not part of the cargo dependency graph but their ABI is coupled to it. They're installed into a workspace-local .dev-tools/ directory (pinned to the dylint_linting version in Cargo.lock) by:

just install-dev-tools

Run this once after cloning, and again whenever dylint_linting is bumped. Every other just recipe prepends .dev-tools/bin to PATH, so subsequent commands use the pinned binaries automatically.

Run the following command to check everything:

just all

Frequently Asked Questions

Why does this code base look so ugly?

This code base is almost entirely AI-generated. Or in other words, vibe-coded.

Why vibe-code?

I needed a way to automatically force the AI agents I use to comply with a certain code style, reducing the time I'll have to spend micro-managing and reviewing AI-generated code. I cannot rely on them interpreting the rules in the Markdown guides correctly, and they often don't comply with the rules completely. Hence, I looked at the code style guides and thought: "Hmm, some of these rules can be coded into a program!" and so this program was born.

I needed encode these rules quick, so I chose vibe-coding.

The code quality of this code base is not as important as the code quality this code base will enforce upon others. This code base is, after all, scaffholding.

License

MIT © Hoàng Văn Khải.

Scan report · 2026-09-12
  • Prohibited terms or links
  • Repository eligibility
  • slopscore.md paperwork
  • Content policy
  • Risk review

0 comments

log in to comment.

report this listinglog in to report