Lib.rs

Issues found

Based on crates you own that have been published to crates.io. The best way to monitor these issues is to subscribe to the atom feed in your RSS reader.

• mut

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

• cmut

  • Failed to verify create's content against its repository

    Partially verified 15 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.

    Fetched https://github.com/miguelferreira18/nar-tool.git 0957bba6f91aa0eae476af53c1a84bee131d6ad8.

    Checked on 2024-08-16

    This check is experimental.

    Forum thread

No issues found in: migas my_cli_tool

If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
status = "deprecated" to their Cargo.toml.