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.

• ft_lib

  • README missing from the repository

    We've searched https://github\.com/luised2094/ft\_lib\_rust\.git and could not find a README file there.

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

  • Published crate doesn't match its repository

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

    Fetched https://github.com/luised2094/ft_lib_rust.git 6509fbbc14d05bba6413ab8d2bfa214b34e3ddd9.

    Checked on 2025-05-28

    This check is experimental.

    Forum thread

• computorv1

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2025-06-11

    Forum thread

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