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.

• emseries

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/luminescent\-dreams/emseries\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • Dependency chrono-tz 0.4 is significantly outdated

    Upgrade to 0.10.3 to get all the fixes, and avoid causing duplicate dependencies in projects.

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    chrono-tz versions

  • Dependency uuid 0.8 is significantly outdated

    Upgrade to 1.16.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    uuid versions

  • Imprecise dependency requirement serde = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as serde = "1.0.219". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    serde versions

  • Dependency dimensioned 0.7 is outdated

    Upgrade to 0.8.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    dimensioned versions

  • Missing keywords

    Help users find your crates. Add keywords = ["database", "emseries", "forms"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• fitnesstrax

  • Dependency chrono-tz 0.4 is significantly outdated

    Consider upgrading to 0.10.3 to get all the fixes and improvements.

    chrono-tz versions

  • Dependency fluent 0.9.1 is significantly outdated

    Consider upgrading to 0.16.1 to get all the fixes and improvements.

    fluent versions

  • Dependency gio 0.8.1 is significantly outdated

    Consider upgrading to 0.20.9 to get all the fixes and improvements.

    gio versions

  • Dependency glib 0.9.0 is significantly outdated

    Consider upgrading to 0.20.9 to get all the fixes and improvements.

    glib versions

  • Dependency gtk 0.8.0 is significantly outdated

    Consider upgrading to 0.18.2 to get all the fixes and improvements.

    gtk versions

  • Dependency serde_yaml 0.8 has issues

    It may not be actively developed any more. Consider changing the dependency.

    serde_yaml crate

  • Dependency unic-langid 0.7.1 is significantly outdated

    Consider upgrading to 0.9.5 to get all the fixes and improvements.

    unic-langid versions

  • Dependency dimensioned 0.7.0 is outdated

    Consider upgrading to 0.8.0 to get all the fixes and improvements.

    dimensioned versions

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'health-and-fitness', which isn't a category we recognize

    lib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["translation", "health-and-fitness", "computer", "timezone"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• orizentic

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/luminescent\-dreams/orizentic\.git

  • Dependency itertools 0.7.8 is significantly outdated

    Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    itertools versions

  • Dependency jsonwebtoken 5 is significantly outdated

    Upgrade to 9.3.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    jsonwebtoken versions

  • Dependency uuid 0.6.5 is significantly outdated

    Upgrade to 1.16.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    uuid versions

  • Dependency version_check 0.1.5 is significantly outdated

    Upgrade to 0.9.5 to get all the fixes, and avoid causing duplicate dependencies in projects.

    version_check versions

  • Dependency clap 2.32.0 is outdated

    Upgrade to 4.5.37 to get all the fixes, and avoid causing duplicate dependencies in projects.

    clap versions

  • Imprecise dependency requirement jsonwebtoken = 5

    Cargo does not always pick latest versions of dependencies! Specify the version as jsonwebtoken = "9.3.0". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with -Z minimal-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.

    jsonwebtoken versions

  • Missing keywords

    Help users find your crates. Add keywords = ["orizentic", "token", "resources"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• fluent-ergonomics

  • Dependency fluent 0.11 is significantly outdated

    Upgrade to 0.16.1 to get all the fixes, and avoid causing duplicate dependencies in projects.

    fluent versions

  • Dependency fluent-syntax ^0.9 is significantly outdated

    Upgrade to 0.11.1 to get all the fixes, and avoid causing duplicate dependencies in projects.

    fluent-syntax versions

  • Dependency unic-langid 0.8 is significantly outdated

    Upgrade to 0.9.5 to get all the fixes, and avoid causing duplicate dependencies in projects.

    unic-langid versions

  • Latest stable release is old

    It's been over 4 years. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

  • Missing keywords

    Help users find your crates. Add keywords = ["fluent", "fluent-ergonomics", "ergonomics", "fluent-rs"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• hex-string

  • Latest stable release is old

    It's been over 6 years. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    Maintenance status field docs

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["hex-string", "representation", "string"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

  • Published crate contains binary files

    The crate contains binary files (rust library). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• micrologger

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/luminescent\-dreams/micrologger\.git

  • Missing keywords

    Help users find your crates. Add keywords = ["micrologger", "from-str", "class"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• emseries, micrologger, orizentic, fitnesstrax-lib

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

• fitnesstrax-lib

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/luminescent\-dreams/fitnesstrax\.git

  • Dependency chrono-tz 0.4 is significantly outdated

    Upgrade to 0.10.3 to get all the fixes, and avoid causing duplicate dependencies in projects.

    chrono-tz versions

  • Imprecise dependency requirement serde = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as serde = "1.0.219". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    serde versions

  • Dependency dimensioned 0.7.0 is outdated

    Upgrade to 0.8.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    dimensioned versions

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'health-and-fitness', which isn't a category we recognize

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["fitnesstrax", "fitnesstrax-lib", "health-and-fitness", "data"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• emseries, micrologger, fitnesstrax, orizentic, fitnesstrax-lib

  • Latest stable release is old

    It's been over 5 years. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    Maintenance status field docs

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