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.

• ncm-api-rs

  • Imprecise dependency requirement serde = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as serde = "1.0.228". 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 aes 0.8 is a bit outdated

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

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

    aes versions

  • Dependency cbc 0.1 is slightly outdated

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

    cbc versions

  • Dependency ecb 0.1 is slightly outdated

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

    ecb versions

  • Dependency md-5 0.10 is a bit outdated

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

    md-5 versions

  • Dependency rand 0.8 is outdated

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

    rand versions

  • Dependency reqwest 0.12 is outdated

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

    reqwest versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["multimedia::audio", "web-programming::http-server"] to the Cargo.toml.

    Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["nodejs", "cookies", "sdk", "music-api", "ncm"] (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.

  • Optional dependency 'axum' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'axum', 'tower', 'tracing', 'tracing-subscriber', 'tower-http' may have been unintentional.

    Crate features

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