The crate is on GitHub only, so the only way to use it is a git dependency and the only way to find it is to already know it exists.
Why this is the highest-value item on the list
crates.io pages rank well in search. Someone typing "SNI 1729 rust" or "perhitungan struktur baja library" will not find a GitHub repository easily, but a crates.io page with a clear description has a real chance. docs.rs then builds and hosts the API documentation for free, which is a second indexed surface with every public item on it.
For a library nobody has heard of, publication is worth more than another feature.
Before publishing
Note
Publishing is close to irreversible: a version can be yanked but not deleted, and the name is taken permanently. Worth being deliberate about the name and the initial API surface.
The crate is on GitHub only, so the only way to use it is a git dependency and the only way to find it is to already know it exists.
Why this is the highest-value item on the list
crates.io pages rank well in search. Someone typing "SNI 1729 rust" or "perhitungan struktur baja library" will not find a GitHub repository easily, but a crates.io page with a clear description has a real chance. docs.rs then builds and hosts the API documentation for free, which is a second indexed surface with every public item on it.
For a library nobody has heard of, publication is worth more than another feature.
Before publishing
cargo publish --dry-runpassesdescription,keywords,categories,repositoryandreadmeare all set inCargo.toml, since those are the searchable fieldscargo publish --dry-runstep to CI so a broken manifest is caught before a release, not during oneNote
Publishing is close to irreversible: a version can be yanked but not deleted, and the name is taken permanently. Worth being deliberate about the name and the initial API surface.