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.

• prest-embed-utils

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["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 = ["framework", "restful", "full-stack", "embed", "progressive"] (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.

• prest

  • Dependency russh 0.48 is significantly outdated

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

    russh versions

  • Dependency russh-keys 0.48.1 is significantly outdated

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

    russh-keys versions

  • Dependency sysinfo 0.32 is significantly outdated

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

    sysinfo versions

  • Dependency tao 0.24 is significantly outdated

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

    tao versions

  • Dependency wry 0.35 is significantly outdated

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

    wry versions

  • Published crate doesn't match its repository

    Verified 74 out of 76 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag '0.5.1'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Repository fetch error: Broken repo: protocol error, missing OIDs or HEAD.
      • Ooops? If this shouldn't happen, file a bug https://gitlab.com/lib.rs/main

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

    • Cargo.toml.orig does not match the repository.
    • Cargo.toml exists, but elsewhere in the repo.
    • mod.rs does not match the repository.

    Fetched https://github.com/edezhic/prest.git tagged 0.5.0 (090fc4f36b424a4caf8c825c0645ef79ce100f72).

    Checked on 2025-01-05

    This check is experimental.

    Forum thread

  • Dependency axum 0.7.9 is outdated

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

    axum versions

  • Dependency axum-htmx 0.6 is slightly outdated

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

    axum-htmx versions

  • Dependency axum-login 0.16 is outdated

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

    axum-login versions

  • Dependency bincode 1 is slightly outdated

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

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

    bincode versions

  • Dependency directories 5.0 is outdated

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

    directories versions

  • Dependency openidconnect 3.5 is outdated

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

    openidconnect versions

  • Dependency rustls-acme 0.12 is outdated

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

    rustls-acme versions

  • Dependency tower-sessions 0.13 is outdated

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

    tower-sessions versions

  • Imprecise dependency requirement iter-enum = 1

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

    iter-enum versions

  • Optional dependency 'axum-login' 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-login', 'password-auth', 'tao', 'gluesql', 'tracing-web', 'hex', 'prest-embed-utils', 'tracing-subscriber', 'bincode', 'openidconnect', 'wry', 'tracing-appender', 'tower-sessions', 'prest-embed-macro', 'prest-db-macro', 'prest-html-macro', 'ansi-to-html' may have been unintentional.

    Crate features

• prest-embed-utils, prest-init-macro, prest-embed-macro, prest-db-macro

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

• prest-build

  • Dependency swc_common 5 is significantly outdated

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

    swc_common versions

  • Dependency swc_ecma_ast 5 is significantly outdated

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

    swc_ecma_ast versions

  • Dependency swc_ecma_codegen 5 is significantly outdated

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

    swc_ecma_codegen versions

  • Dependency swc_ecma_loader 5 is significantly outdated

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

    swc_ecma_loader versions

  • Dependency swc_ecma_minifier 6 is significantly outdated

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

    swc_ecma_minifier versions

  • Dependency swc_ecma_parser 6 is significantly outdated

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

    swc_ecma_parser versions

  • Dependency swc_ecma_transforms_base 6 is significantly outdated

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

    swc_ecma_transforms_base versions

  • Dependency swc_ecma_transforms_react 6 is significantly outdated

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

    swc_ecma_transforms_react versions

  • Dependency swc_ecma_transforms_typescript 6 is significantly outdated

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

    swc_ecma_transforms_typescript versions

  • Dependency swc_ecma_visit 5 is significantly outdated

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

    swc_ecma_visit versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency swc_bundler 6 is outdated

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

    swc_bundler versions

  • Optional dependency 'swc_common' 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 'swc_common', 'wasm-bindgen-cli-support', 'swc_ecma_codegen', 'swc_ecma_transforms_react', 'swc_ecma_loader', 'swc_ecma_transforms_typescript', 'swc_ecma_visit', 'swc_bundler', 'swc_ecma_parser', 'grass', 'swc_ecma_minifier', 'swc_ecma_transforms_base', 'webmanifest', 'swc_ecma_ast' may have been unintentional.

    Crate features

• prest-embed-utils, prest-build, prest-serde-derive-fork, prest-html-macro, prest-init-macro, prest-embed-macro, prest-db-macro

  • No readme property

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

• prest-embed-utils, prest-build, prest-embed-macro, prest-db-macro

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/edezhic/prest\.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.

• prest-html-macro

  • Failed to verify create's content against its repository

    Verified 2 out of 10 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).

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

    • tailwind.rs not found.
    • generate.rs not found.
    • parse.rs not found.
    • lib.rs not found.
    • Cargo.toml.orig does not match the repository.
    • ast.rs not found.
    • escape.rs exists, but elsewhere in the repo.
    • htmx.rs not found.

    Fetched https://github.com/lambda-fairy/maud.git c13e1dcc489d1132e56c7284af49c620f7345b91.

    Checked on 2024-12-29

    Forum thread

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/lambda\-fairy/maud\.git

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• prest-serde-derive-fork

  • Failed to verify create's content against its repository

    Verified 2 out of 21 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).

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

    • Cargo.toml.orig does not match the repository.
    • src/
      • lib.rs exists, but elsewhere in the repo.
      • bound.rs exists, but elsewhere in the repo.
      • pretend.rs exists, but elsewhere in the repo.
      • ser.rs exists, but elsewhere in the repo.
      • de.rs exists, but elsewhere in the repo.
      • dummy.rs exists, but elsewhere in the repo.
      • fragment.rs exists, but elsewhere in the repo.
      • this.rs exists, but elsewhere in the repo.
    • src/internals/
      • ast.rs exists, but elsewhere in the repo.
      • respan.rs exists, but elsewhere in the repo.
      • check.rs exists, but elsewhere in the repo.
      • name.rs exists, but elsewhere in the repo.
      • ctxt.rs exists, but elsewhere in the repo.
      • receiver.rs exists, but elsewhere in the repo.
      • case.rs exists, but elsewhere in the repo.
      • mod.rs exists, but elsewhere in the repo.
      • attr.rs not found.
      • symbol.rs exists, but elsewhere in the repo.

    Fetched https://github.com/serde-rs/serde.git tagged v1.0.216 (ad8dd4148b5fabf0d643d4de604a0616f2796506).

    Checked on 2025-01-12

    Forum thread

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.61, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• prest-db-macro

  • Published crate doesn't match its repository

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

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag '0.4.0'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

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

    • Cargo.toml.orig does not match the repository.
    • from_glue_value.rs does not match the repository.
    • expand.rs does not match the repository.
    • db/macro/
      • expand.rs exists, but elsewhere in the repo.
      • from_glue_value.rs exists, but elsewhere in the repo.
      • Cargo.toml exists, but elsewhere in the repo.

    Looked for the crate in db/macro/. Fetched https://github.com/edezhic/prest.git tagged 0.4.1 (8bc3190c6188c33fe857d39794a86216e94dc1b9).

    Checked on 2025-01-12

    Forum thread

  • Imprecise dependency requirement syn = 2

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

    syn versions

• prest-embed-macro

  • Published crate doesn't match its repository

    Verified 2 out of 4 files (includes 2 Cargo-generated).

    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.
    • embed/macro/
      • Cargo.toml exists, but elsewhere in the repo.
      • lib.rs exists, but elsewhere in the repo.

    Looked for the crate in embed/macro/. Fetched https://github.com/edezhic/prest.git tagged 0.4.1 (8bc3190c6188c33fe857d39794a86216e94dc1b9).

    Checked on 2024-12-29

    Forum thread

  • Imprecise dependency requirement shellexpand = 3

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

    shellexpand versions

• prest-init-macro

  • Imprecise dependency requirement syn = 2

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

    syn versions

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