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.

• gdnative_bindings_generator

  • Dependency roxmltree 0.17 is significantly outdated

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

    roxmltree versions

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement syn = 1

    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.

    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

  • Dependency heck 0.4 is outdated

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

    heck versions

  • Dependency which 4 is a bit outdated

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

    which versions

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "api-bindings", "json-api", "native-bindings", "bindings-generator"] (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 'which' 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 'which' may have been unintentional.

    Crate features

• gdextension-api, godot-bindings, godot-ffi, godot-cell, godot-codegen, godot-core, godot-macros

  • No readme property

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

• gdnative

  • Optional dependency 'gdnative-async' 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 'gdnative-async' may have been unintentional.

    Crate features

• gdnative, gdnative_bindings_generator, gdnative-bindings, gdnative-async, gdnative-sys, gdnative-core

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["game-development"] 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

• js-sandbox

  • Latest prerelease is old

    It's been over 17 months. 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").

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

  • Reported security advisory RUSTSEC-2024-0403

    op_panic in the base runtime can force a panic in the runtime's containing thread

    All crate audits

  • Dependency deno_core 0.209.0 is significantly outdated

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

    deno_core versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["javascript", "sandbox", "js", "plugin", "secure"] (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.

• godot-bindings

  • Dependency bindgen 0.68 is significantly outdated

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

    bindgen versions

  • Dependency which 6 is significantly outdated

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

    which versions

• godot-core

  • Dependency glam 0.28 is significantly outdated

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

    glam versions

  • Imprecise dependency requirement serde = 1

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

• gdnative_bindings_generator, gdnative-bindings, gdnative-async, gdnative-sys, gdnative-core, js-sandbox-macros

  • 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.

• godot-bindings, godot-cell, godot-macros

  • 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

• gdnative-async

  • Imprecise dependency requirement atomic-waker = 1

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

    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.

    atomic-waker versions

  • Missing keywords

    Help users find your crates. Add keywords = ["native-bindings", "godot", "async", "game-engine", "run-time"] (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.

• gdnative-sys

  • Dependency bindgen 0.63.0 is significantly outdated

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

    bindgen versions

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "gdnative" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "bindings", "native-bindings", "engine", "game-engine"] (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.

• gdnative-bindings

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "generated-bindings", "game-engine", "native-bindings", "api-bindings"] (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.

• gdnative-core

  • Dependency glam 0.22 is significantly outdated

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

    glam versions

  • Dependency bitflags 1 is outdated

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

    bitflags versions

  • Dependency indexmap 1 is outdated

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

    indexmap versions

  • Imprecise dependency requirement atomic-take = 1

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

    atomic-take versions

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "game-engine", "interface", "bindings", "reference"] (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.

• godot-classes

  • Failed to verify create's content against its repository

    Verified 3 out of 6 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 719c1e09b58c7b60b0fa506f3242709330dd07a5, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

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

    Fetched https://github.com/godot-rust/gdext.git f6a309af45a773b5f858fe70ffe53f4856caf197.

    Checked on 2025-02-16

    This check is experimental.

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "bindings", "api", "language", "png"] (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.

  • No readme property

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

• godot-classes, godot-rust, godot-cli, gdext, godot-derive

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["…"] to the Cargo.toml.

    List of available categories

• godot-macros

  • Published crate doesn't match its repository

    Partially verified 39 files (includes 3 Cargo-generated).

    • error: Cargo.toml and Cargo.toml.orig had different [features]

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

    • Cargo.lock not found.

    Looked for the crate in godot-macros/. Fetched https://github.com/godot-rust/gdext.git tagged v0.2.4 (9530704e901953a6e8a9c9d4718f250d4b11f772).

    Checked on 2025-03-02

    Forum thread

  • Dependency markdown =1.0.0-alpha.21 is outdated

    Upgrade to 1.0.0-alpha.23 to get all the fixes, and avoid causing duplicate dependencies in projects.

    markdown versions

• gdnative-impl-proc-macros

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement syn = 1

    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

• gdnative-derive

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Dependency proc-macro-crate 1 is outdated

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

    proc-macro-crate versions

  • Imprecise dependency requirement proc-macro-crate = 1

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

    proc-macro-crate versions

• js-sandbox-macros

  • Latest prerelease is old

    It's been over 17 months. 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

• godot-cli

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit 1f207ca1de37d1e3d20af61fbc5765c11891aeac, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

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

    Fetched https://github.com/godot-rust/gdext.git 421324a9087e34c1bd1513cb4e129078b18e616a.

    Checked on 2024-07-24

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "bindings", "api", "language", "png"] (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.

• gdext

  • Failed to verify create's content against its repository

    Verified 2 out of 5 files (includes 2 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 323fdd7c11165e5f64ad260d90754adc822aba43, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Could not discover crate's location in its repository (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • warning: There is no matching git tag containing version '0.0.0'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

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

    Fetched https://github.com/godot-rust/gdextension.git e25e9942487957b9f09f72ee008288230b626dbd.

    Checked on 2024-07-28

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "bindings", "api"] (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.

• gdnative-impl-proc-macros, gdnative-derive, godot-test, godot-async, godot-rust, godot-wasm, godot-cli, gdext, godot-derive

  • 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.

• godot-test

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["game-development"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "native-bindings", "engine", "develop", "gamedev"] (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.

• godot-async

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["game-development"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "bindings", "gamedev", "native-bindings", "hello-world"] (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.

• godot-rust

  • Latest stable release is old

    It's been over 3 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 = ["godot", "bindings", "native-bindings", "now"] (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.

• godot-wasm

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["wasm", "game-development"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "bindings", "gamedev", "game", "native-bindings"] (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.

• godot-derive

  • Latest stable release is old

    It's been over 3 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

  • Missing keywords

    Help users find your crates. Add keywords = ["godot", "bindings", "derive", "native-bindings", "hello-world"] (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.

• gdnative-project-utils

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

  • Dependency path-slash 0.1 is outdated

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

    path-slash versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::build-utils"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["gd-native", "projects", "generate", "build-script", "directory"] (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.

• gdextension

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• decentral

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/decentral ). Please try again later.

• nav

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/nav ). Please try again later.

• thor

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/thor ). Please try again later.

No issues found in: godot venial

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