What needs doing
The [package] block has no keywords, no categories and no homepage, so sqwatch shows up under no category listing on crates.io and matches no keyword search. Four lines:
keywords = ["slurm", "hpc", "tui", "cluster", "ratatui"]
categories = ["command-line-utilities", "science"]
homepage = "https://github.com/fedonman/sqwatch"
categories has to come from the fixed crates.io list and an invalid slug fails the upload, so check both slugs against the current list before publishing. Keywords are capped at five, twenty characters each.
Leaving documentation out on purpose. docs.rs hosts the lib target's rustdoc automatically, and the public API here is an implementation detail rather than something to point users at. The README is the documentation and readme already points at it.
Why
Launch traffic is one-shot, it arrives and then decays. Categories and keywords are the durable half: they keep working long after the threads are archived, and they are the only way someone browsing crates.io for a SLURM or HPC tool ever finds this. It costs four lines and no code.
Worth doing in the same pass, since it is the same kind of gap: CI runs only on pull requests and pushes to main, so cargo-deny sees an advisory only when someone happens to open a PR, and a quiet month means nobody hears about one. A scheduled run fixes that, and there is no .github/dependabot.yml at all today, so cargo and github-actions updates are entirely manual.
What needs doing
The
[package]block has nokeywords, nocategoriesand nohomepage, so sqwatch shows up under no category listing on crates.io and matches no keyword search. Four lines:categorieshas to come from the fixed crates.io list and an invalid slug fails the upload, so check both slugs against the current list before publishing. Keywords are capped at five, twenty characters each.Leaving
documentationout on purpose. docs.rs hosts the lib target's rustdoc automatically, and the public API here is an implementation detail rather than something to point users at. The README is the documentation andreadmealready points at it.Why
Launch traffic is one-shot, it arrives and then decays. Categories and keywords are the durable half: they keep working long after the threads are archived, and they are the only way someone browsing crates.io for a SLURM or HPC tool ever finds this. It costs four lines and no code.
Worth doing in the same pass, since it is the same kind of gap: CI runs only on pull requests and pushes to main, so
cargo-denysees an advisory only when someone happens to open a PR, and a quiet month means nobody hears about one. A scheduled run fixes that, and there is no.github/dependabot.ymlat all today, socargoandgithub-actionsupdates are entirely manual.