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.

• roto

  • Dependency cranelift-codegen 0.120.0 is significantly outdated

    Upgrade to 0.124.1 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.

    cranelift-codegen versions

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency cranelift 0.120.0 is outdated

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

    cranelift versions

  • Dependency rustc-literal-escaper 0.0.4 is a bit outdated

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

    rustc-literal-escaper versions

  • Dependency symbol_table 0.4.0 is outdated

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

    symbol_table versions

  • Optional dependency 'clap' 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 'clap', 'env_logger' may have been unintentional.

    Crate features

• rotonda-store

  • Dependency ansi_term 0.12 has issues

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

    ansi_term crate

  • Dependency roaring 0.10.3 is slightly outdated

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

    roaring versions

  • Dependency routecore 0.5.2 is outdated

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

    routecore versions

  • Dependency rustyline 15 is outdated

    Upgrade to 17.0.1 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.

    rustyline versions

  • Imprecise dependency requirement csv = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as csv = "1.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.

    csv versions

  • Optional dependency 'rayon' 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 'rayon', 'clap', 'rustyline', 'ansi_term', 'csv' may have been unintentional.

    Crate features

• routecore

  • Dependency const-str 0.6 is significantly outdated

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

    const-str versions

  • Optional dependency 'bytes' 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 'bytes', 'octseq', 'rayon', 'serde', 'tokio', 'log', 'chrono', 'const-str' may have been unintentional.

    Crate features

• rotonda

  • Dependency bzip2 0.5.0 is significantly outdated

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

    bzip2 versions

  • Dependency hashbrown 0.14 is significantly outdated

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

    hashbrown versions

  • Dependency rumqttc 0.23.0 is significantly outdated

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

    rumqttc versions

  • Dependency allocator-api2 0.2 is slightly outdated

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

    allocator-api2 versions

  • Dependency atomic_enum 0.2.0 is outdated

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

    atomic_enum versions

  • Dependency fern 0.6 is outdated

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

    fern versions

  • Dependency hash32 0.3.1 is outdated

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

    hash32 versions

  • Dependency hyper 0.14 is outdated

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

    hyper versions

  • Dependency micromap 0.0.19 is outdated

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

    micromap versions

  • Dependency rand 0.8 is outdated

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

    rand versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency rshtml 0.2.0 is slightly outdated

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

    rshtml versions

  • Dependency syslog 6.1 is outdated

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

    syslog versions

  • Dependency tokio-metrics 0.3 is outdated

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

    tokio-metrics versions

  • Dependency toml 0.8 is outdated

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

    toml versions

  • Imprecise dependency requirement serde_with = 3

    Cargo does not always pick latest versions of dependencies! Specify the version as serde_with = "3.14.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.

    serde_with versions

  • Optional dependency 'flate2' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'flate2' may have been unintentional.

    Crate features

• routinator-ui

  • 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

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Detecting docs.rs

  • Dependency reqwest 0.11.0 is outdated

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

    reqwest versions

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'web-ui', 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

  • 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

• rotonda-fsm

  • Dependency octseq 0.4.0 is significantly outdated

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

    octseq versions

  • Dependency routecore 0.4.0 is outdated

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

    routecore versions

  • Imprecise dependency requirement tokio = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as tokio = "1.47.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.

    tokio versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["network-programming"] 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 = ["finite-state-machine", "bgp", "rotonda", "session", "setup"] (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.

• rotonda-macros

  • Failed to verify create's content against its repository

    Verified 5 out of 8 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Crate tarball has been published from the commit a406498fa169a2c25b7c181a51d7f0cbd28b1790, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Could not discover crate's location in its repository (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: can't load root workspace: Can't find workspace in //...
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: Can't find workspace in //...
    • error: Manifest properties don't match: package.version.
      • If you have a monorepo, you can use git tags in format cratename/v0.4.0

    Files in the crates.io crate compared to the repository:

    • Cargo.toml.orig does not match the repository.
    • lib.rs does not match the repository.

    Fetched https://github.com/nlnetlabs/rotonda-macros.git 926654da83ccb577594b05c1c0e2712e6579d4c3.

    Checked on 2025-04-29

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement syn = ^2

    Cargo does not always pick latest versions of dependencies! Specify the version as syn = "2.0.106". 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.

    syn versions

No issues found in: roto-macros

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