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.

• kalosm

  • Published crate doesn't match its repository

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

    • error: Cargo.lock was suspiciously large.
      • If you don't need this file, use include or exclude in Cargo.toml, otherwise file a bug at https://gitlab.com/lib.rs/main
    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in interfaces/kalosm/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-16

    This check is experimental.

    Forum thread

  • Dependency heed 0.20.5 is a bit outdated

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

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

    heed versions

• kalosm, kalosm-language, kalosm-sample, kalosm-language-model, kalosm-streams, rbert, kalosm-learning, kalosm-llama, kalosm-model-types

  • Missing categories

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

• kalosm, kalosm-language, kalosm-sound, kalosm-language-model, rwhisper, kalosm-learning, kalosm-llama

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

• kalosm, kalosm-language, kalosm-sound, kalosm-sample, kalosm-language-model, kalosm-streams, rbert, rwhisper, kalosm-vision, kalosm-learning, kalosm-llama, kalosm-model-types, rwuerstchen

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

    Use OR instead of /.

    SPDX license list

• manganis-common

  • Missing categories

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

    List of available categories

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/dioxuslabs/manganis\.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 infer 0.11.0 is significantly outdated

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

    infer versions

  • Dependency toml 0.7.6 is significantly outdated

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

    toml versions

  • Imprecise dependency requirement anyhow = 1

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

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

  • 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

  • Dependency base64 0.21.5 is outdated

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

    base64 versions

  • Latest prerelease is old

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

• kalosm-sound

  • Dependency ort =2.0.0-rc.4 is significantly outdated

    Upgrade to 2.0.0-rc.9 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.

    ort versions

  • Dependency ort-sys =2.0.0-rc.4 is significantly outdated

    Upgrade to 2.0.0-rc.9 to get all the fixes, and avoid causing duplicate dependencies in projects.

    ort-sys versions

  • Published crate doesn't match its repository

    Partially verified 18 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in interfaces/kalosm-sound/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-16

    Forum thread

  • Missing categories

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

    List of available categories

• manganis

  • Failed to verify create's content against its repository

    Verified 1 out of 10 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 5d4893493b6116d8b39199a6d7028dd287d509da, 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: There is no matching git tag containing version '0.6.2'.
    • 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: workspace dependencies are missing `const-serialize`.
    • error: Dependencies don't match: 'const-serialize' uses workspace inheritance, but the root workspace is not available.
      • Make sure to commit and tag after updating Cargo.toml
    • error: Dependencies don't match: 'manganis-core' uses workspace inheritance, but the root workspace is not available.
    • error: Dependencies don't match: 'manganis-macro' uses workspace inheritance, but the root workspace is not available.
    • error: Manifest properties don't match: package.version.
      • If you have a monorepo, you can use git tags in format cratename/v0.6.2

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

    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • assets/
      • image.png not found.
      • script.js does not match the repository.
      • style.css exists, but elsewhere in the repo.
    • src/
      • macro_helpers.rs not found.
      • hash.rs not found.
      • lib.rs does not match the repository.

    Fetched https://github.com/dioxuslabs/manganis.git 00b8a5c0d1b2101b52998a577d383b436818dba0.

    Checked on 2025-01-26

    Forum thread

  • 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

• kalosm-language

  • Published crate doesn't match its repository

    Partially verified 32 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in interfaces/kalosm-language/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-16

    Forum thread

  • Dependency convert_case 0.6.0 is a bit outdated

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

    convert_case versions

  • Dependency dashmap 5.5.3 is outdated

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

    dashmap versions

  • Dependency ego-tree 0.6.2 is a bit outdated

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

    ego-tree versions

  • Dependency heed 0.20.0-alpha.9 is a bit outdated

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

    heed versions

  • Dependency pulldown-cmark 0.9.3 is outdated

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

    pulldown-cmark versions

  • Dependency readability 0.2.0 is outdated

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

    readability versions

  • Dependency reqwest 0.11.18 is outdated

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

    reqwest versions

  • Dependency scraper 0.19.0 is outdated

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

    scraper versions

• sledgehammer_utils

  • README missing from the repository

    We've searched https://github\.com/demonthos/sledgehammer\_utils\.git and could not find a README file there.

  • No readme property

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

  • Dependency rustc-hash 1.1.0 is a bit outdated

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

    rustc-hash versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["sledgehammer", "sledgehammer-bindgen", "sledgehammer-utils"] (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.

• manganis-cli-support

  • Dependency swc =0.283.0 is significantly outdated

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

    swc versions

  • Dependency swc_allocator =0.1.8 is significantly outdated

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

    swc_allocator versions

  • Dependency swc_common =0.37.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_compiler_base =0.19.0 is significantly outdated

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

    swc_compiler_base versions

  • Dependency swc_ecma_codegen =0.155.1 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_compat_bugfixes =0.12.0 is significantly outdated

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

    swc_ecma_compat_bugfixes versions

  • Dependency swc_ecma_compat_common =0.11.0 is significantly outdated

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

    swc_ecma_compat_common versions

  • Dependency swc_ecma_compat_es2015 =0.12.0 is significantly outdated

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

    swc_ecma_compat_es2015 versions

  • Dependency swc_ecma_compat_es2016 =0.12.0 is significantly outdated

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

    swc_ecma_compat_es2016 versions

  • Dependency swc_ecma_compat_es2017 =0.12.0 is significantly outdated

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

    swc_ecma_compat_es2017 versions

  • Dependency swc_ecma_compat_es2018 =0.12.0 is significantly outdated

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

    swc_ecma_compat_es2018 versions

  • Dependency swc_ecma_compat_es2019 =0.12.0 is significantly outdated

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

    swc_ecma_compat_es2019 versions

  • Dependency swc_ecma_compat_es2020 =0.12.0 is significantly outdated

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

    swc_ecma_compat_es2020 versions

  • Dependency swc_ecma_compat_es2021 =0.12.0 is significantly outdated

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

    swc_ecma_compat_es2021 versions

  • Dependency swc_ecma_compat_es2022 =0.12.0 is significantly outdated

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

    swc_ecma_compat_es2022 versions

  • Dependency swc_ecma_compat_es3 =0.12.0 is significantly outdated

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

    swc_ecma_compat_es3 versions

  • Dependency swc_ecma_ext_transforms =0.120.0 is significantly outdated

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

    swc_ecma_ext_transforms versions

  • Dependency swc_ecma_lints =0.100.0 is significantly outdated

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

    swc_ecma_lints versions

  • Dependency swc_ecma_loader =0.49.1 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 =0.204.0 is significantly outdated

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

    swc_ecma_minifier versions

  • Dependency swc_ecma_preset_env =0.217.0 is significantly outdated

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

    swc_ecma_preset_env versions

  • Dependency swc_ecma_transforms =0.239.0 is significantly outdated

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

    swc_ecma_transforms versions

  • Dependency swc_ecma_transforms_base =0.145.0 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_classes =0.134.0 is significantly outdated

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

    swc_ecma_transforms_classes versions

  • Dependency swc_ecma_transforms_compat =0.171.0 is significantly outdated

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

    swc_ecma_transforms_compat versions

  • Dependency swc_ecma_transforms_module =0.190.0 is significantly outdated

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

    swc_ecma_transforms_module versions

  • Dependency swc_ecma_transforms_optimization =0.208.0 is significantly outdated

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

    swc_ecma_transforms_optimization versions

  • Dependency swc_ecma_transforms_proposal =0.178.0 is significantly outdated

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

    swc_ecma_transforms_proposal versions

  • Dependency swc_ecma_transforms_react =0.191.0 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 =0.198.1 is significantly outdated

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

    swc_ecma_transforms_typescript versions

  • Dependency swc_ecma_usage_analyzer =0.30.3 is significantly outdated

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

    swc_ecma_usage_analyzer versions

  • Dependency swc_ecma_utils =0.134.2 is significantly outdated

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

    swc_ecma_utils versions

  • Dependency swc_ecma_visit =0.104.8 is significantly outdated

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

    swc_ecma_visit versions

  • Dependency swc_error_reporters =0.21.0 is significantly outdated

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

    swc_error_reporters versions

  • Dependency swc_macros_common =0.3.13 is significantly outdated

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

    swc_macros_common versions

  • Dependency swc_node_comments =0.24.0 is significantly outdated

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

    swc_node_comments versions

  • Dependency swc_timer =0.25.0 is significantly outdated

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

    swc_timer versions

  • Dependency swc_transform_common =0.1.1 is significantly outdated

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

    swc_transform_common versions

  • Dependency swc_typescript =0.5.0 is significantly outdated

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

    swc_typescript versions

  • Dependency swc_visit =0.6.2 is significantly outdated

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

    swc_visit versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Locked dependency version swc =0.283.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc versions

  • Locked dependency version swc_allocator =0.1.8

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_allocator versions

  • Locked dependency version swc_atoms =0.6.7

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_atoms versions

  • Locked dependency version swc_cached =0.3.20

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_cached versions

  • Locked dependency version swc_common =0.37.5

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_common versions

  • Locked dependency version swc_compiler_base =0.19.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_compiler_base versions

  • Locked dependency version swc_config =0.1.15

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_config versions

  • Locked dependency version swc_config_macro =0.1.4

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_config_macro versions

  • Locked dependency version swc_ecma_ast =0.118.2

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_ast versions

  • Locked dependency version swc_ecma_codegen =0.155.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_codegen versions

  • Locked dependency version swc_ecma_codegen_macros =0.7.7

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_codegen_macros versions

  • Locked dependency version swc_ecma_compat_bugfixes =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_bugfixes versions

  • Locked dependency version swc_ecma_compat_common =0.11.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_common versions

  • Locked dependency version swc_ecma_compat_es2015 =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_es2015 versions

  • Locked dependency version swc_ecma_compat_es2016 =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_es2016 versions

  • Locked dependency version swc_ecma_compat_es2017 =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_es2017 versions

  • Locked dependency version swc_ecma_compat_es2018 =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_es2018 versions

  • Locked dependency version swc_ecma_compat_es2019 =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_es2019 versions

  • Locked dependency version swc_ecma_compat_es2020 =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_es2020 versions

  • Locked dependency version swc_ecma_compat_es2021 =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_es2021 versions

  • Locked dependency version swc_ecma_compat_es2022 =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_es2022 versions

  • Locked dependency version swc_ecma_compat_es3 =0.12.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_compat_es3 versions

  • Locked dependency version swc_ecma_ext_transforms =0.120.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_ext_transforms versions

  • Locked dependency version swc_ecma_lints =0.100.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_lints versions

  • Locked dependency version swc_ecma_loader =0.49.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_loader versions

  • Locked dependency version swc_ecma_minifier =0.204.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_minifier versions

  • Locked dependency version swc_ecma_parser =0.149.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_parser versions

  • Locked dependency version swc_ecma_preset_env =0.217.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_preset_env versions

  • Locked dependency version swc_ecma_transforms =0.239.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms versions

  • Locked dependency version swc_ecma_transforms_base =0.145.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms_base versions

  • Locked dependency version swc_ecma_transforms_classes =0.134.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms_classes versions

  • Locked dependency version swc_ecma_transforms_compat =0.171.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms_compat versions

  • Locked dependency version swc_ecma_transforms_macros =0.5.5

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms_macros versions

  • Locked dependency version swc_ecma_transforms_module =0.190.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms_module versions

  • Locked dependency version swc_ecma_transforms_optimization =0.208.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms_optimization versions

  • Locked dependency version swc_ecma_transforms_proposal =0.178.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms_proposal versions

  • Locked dependency version swc_ecma_transforms_react =0.191.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms_react versions

  • Locked dependency version swc_ecma_transforms_typescript =0.198.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_transforms_typescript versions

  • Locked dependency version swc_ecma_usage_analyzer =0.30.3

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_usage_analyzer versions

  • Locked dependency version swc_ecma_utils =0.134.2

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_utils versions

  • Locked dependency version swc_ecma_visit =0.104.8

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_ecma_visit versions

  • Locked dependency version swc_eq_ignore_macros =0.1.4

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_eq_ignore_macros versions

  • Locked dependency version swc_error_reporters =0.21.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_error_reporters versions

  • Locked dependency version swc_fast_graph =0.25.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_fast_graph versions

  • Locked dependency version swc_macros_common =0.3.13

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_macros_common versions

  • Locked dependency version swc_node_comments =0.24.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_node_comments versions

  • Locked dependency version swc_timer =0.25.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_timer versions

  • Locked dependency version swc_trace_macro =0.1.3

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_trace_macro versions

  • Locked dependency version swc_transform_common =0.1.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_transform_common versions

  • Locked dependency version swc_typescript =0.5.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_typescript versions

  • Locked dependency version swc_visit =0.6.2

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    swc_visit versions

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

    More info

  • Dependency rustc-hash 1.1.0 is a bit outdated

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

    rustc-hash versions

  • Dependency swc_atoms =0.6.7 is outdated

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

    swc_atoms versions

  • Dependency swc_cached =0.3.20 is outdated

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

    swc_cached versions

  • Dependency swc_config =0.1.15 is outdated

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

    swc_config versions

  • Dependency swc_config_macro =0.1.4 is outdated

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

    swc_config_macro versions

  • Dependency swc_ecma_ast =0.118.2 is 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_macros =0.7.7 is outdated

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

    swc_ecma_codegen_macros versions

  • Dependency swc_ecma_parser =0.149.1 is outdated

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

    swc_ecma_parser versions

  • Dependency swc_ecma_transforms_macros =0.5.5 is outdated

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

    swc_ecma_transforms_macros versions

  • Dependency swc_eq_ignore_macros =0.1.4 is outdated

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

    swc_eq_ignore_macros versions

  • Dependency swc_fast_graph =0.25.0 is outdated

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

    swc_fast_graph versions

  • Dependency swc_trace_macro =0.1.3 is outdated

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

    swc_trace_macro versions

  • Latest prerelease is old

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

  • 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

• rwuerstchen

  • Published crate doesn't match its repository

    Partially verified 7 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in models/rwuerstchen/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-23

    Forum thread

  • Dependency hf-hub 0.3.0 is a bit outdated

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

    hf-hub versions

  • Missing categories

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

    List of available categories

• segment-anything-rs

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/floneum/floneum\.git

  • No readme property

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

  • Dependency cudarc 0.9.14 is outdated

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

    cudarc versions

  • Dependency hf-hub 0.3.0 is a bit outdated

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

    hf-hub versions

  • Dependency image 0.24.7 is outdated

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

    image versions

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

    Use OR instead of /.

    SPDX license list

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["science::ml", "multimedia::images"] to the Cargo.toml.

    List of available categories

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

    Crate features

• kalosm-ocr

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/floneum/floneum\.git

  • No readme property

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

  • Dependency cudarc 0.9.14 is outdated

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

    cudarc versions

  • Dependency hf-hub 0.3.0 is a bit outdated

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

    hf-hub versions

  • Dependency image 0.24.7 is outdated

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

    image versions

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

    Use OR instead of /.

    SPDX license list

  • Missing categories

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

    List of available categories

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

    Crate features

• kalosm-vision

  • Published crate doesn't match its repository

    Partially verified 6 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in interfaces/kalosm-vision/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-16

    Forum thread

  • Missing categories

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

    List of available categories

• warnings

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/dioxuslabs/warnings\.git

  • No readme property

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

  • Imprecise dependency requirement pin-project = 1

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

    pin-project versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["debugging", "run-time", "opt-out"] (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.

• rbert

  • 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

  • Published crate doesn't match its repository

    Partially verified 18 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in models/rbert/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-16

    Forum thread

  • Dependency metal 0.27.0 is significantly outdated

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

    metal versions

• kalosm-learning

  • Published crate doesn't match its repository

    Partially verified 10 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in interfaces/kalosm-learning/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-23

    Forum thread

• kalosm-llama

  • Locked dependency version llm-samplers =0.0.7

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    llm-samplers versions

  • Published crate doesn't match its repository

    Partially verified 23 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in models/kalosm-llama/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-16

    Forum thread

  • Dependency safetensors 0.4.5 is outdated

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

    safetensors versions

• kalosm-common

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/floneum/floneum\.git

  • No readme property

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

  • Dependency dirs 5.0.1 is outdated

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

    dirs versions

  • Dependency hf-hub 0.3.0 is a bit outdated

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

    hf-hub versions

  • Dependency metal 0.29.0 is outdated

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

    metal versions

  • Dependency reqwest 0.11.24 is outdated

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

    reqwest versions

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

    Use OR instead of /.

    SPDX license list

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["candle", "download", "kalosm", "utilities", "helper"] (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.

• dioxus-sdk

  • Dependency async-broadcast 0.5.1 is outdated

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

    async-broadcast versions

  • Dependency copypasta 0.8.2 is outdated

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

    copypasta versions

  • Dependency directories 4.0.1 is outdated

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

    directories versions

  • Dependency rustc-hash 1.1.0 is a bit outdated

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

    rustc-hash versions

  • Dependency windows 0.48.0 is outdated

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

    windows versions

  • Dependency yazi 0.1.4 is outdated

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

    yazi versions

  • Optional dependency 'uuid' 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 'uuid', 'web-sys', 'windows' may have been unintentional.

    Crate features

• kalosm-language-model

  • Locked dependency version llm-samplers =0.0.7

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    llm-samplers versions

  • Dependency lru 0.12.3 is a bit outdated

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

    lru versions

  • Failed to verify create's content against its repository

    Partially verified 30 files (includes 4 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.

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

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

    Looked for the crate in interfaces/language-model/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-16

    Forum thread

• rphi

  • Published crate doesn't match its repository

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

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

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

    Looked for the crate in models/rphi/. Fetched https://github.com/floneum/floneum.git 5c03baf16ed1f903c297f3f1105325855489fc29.

    Checked on 2024-08-16

    Forum thread

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/floneum/floneum\.git

  • Dependency candle-nn 0.6.0 is significantly outdated

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

    candle-nn versions

  • Dependency candle-transformers 0.6.0 is significantly outdated

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

    candle-transformers versions

  • Dependency kalosm-common 0.3.0 is significantly outdated

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

    kalosm-common versions

  • Dependency kalosm-language-model 0.3.0 is significantly outdated

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

    kalosm-language-model versions

  • Dependency kalosm-sample 0.3.0 is significantly outdated

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

    kalosm-sample versions

  • Locked dependency version llm-samplers =0.0.7

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    llm-samplers versions

  • No readme property

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

  • Dependency candle-core 0.6.0 is outdated

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

    candle-core versions

  • Dependency cudarc 0.9.14 is outdated

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

    cudarc versions

  • Dependency kalosm-streams 0.3.0 is outdated

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

    kalosm-streams versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency tokenizers 0.19.1 is outdated

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

    tokenizers versions

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

    Use OR instead of /.

    SPDX license list

  • Missing categories

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

    List of available categories

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

    Crate features

• rwhisper

  • Published crate doesn't match its repository

    Partially verified 15 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in models/rwhisper/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-23

    Forum thread

  • Dependency hf-hub 0.3.1 is a bit outdated

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

    hf-hub versions

  • Missing categories

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

    List of available categories

• kalosm-sample, kalosm-language-model, kalosm-streams, rbert, rwhisper, kalosm-learning, kalosm-llama, kalosm-model-types, rwuerstchen

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/floneum/floneum\.git

• kalosm-sample

  • Published crate doesn't match its repository

    Partially verified 25 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in interfaces/kalosm-sample/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-16

    Forum thread

• kalosm-sample, kalosm-language-model, kalosm-streams, rbert, rwhisper, kalosm-learning, kalosm-llama, kalosm-model-types, rwuerstchen

  • No readme property

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

• dioxus-cli

  • Dependency brotli 6.0.0 is significantly outdated

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

    brotli versions

  • Dependency built =0.7.4 is significantly outdated

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

    built versions

  • Dependency console-subscriber 0.3.0 is significantly outdated

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

    console-subscriber versions

  • Dependency ratatui 0.28.0 is significantly outdated

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

    ratatui versions

  • Dependency tauri-utils =2.0.2 is significantly outdated

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

    tauri-utils versions

  • Dependency throbber-widgets-tui =0.7.0 is significantly outdated

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

    throbber-widgets-tui versions

  • Published crate doesn't match its repository

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

    • error: Cargo.lock was suspiciously large.
      • If you don't need this file, use include or exclude in Cargo.toml, otherwise file a bug at https://gitlab.com/lib.rs/main

    Looked for the crate in packages/cli/. Fetched https://github.com/dioxuslabs/dioxus.git tagged v0.6.3 (fc1f1c26f1b5e732c958c83a1665a0a7e5efd205).

    Checked on 2025-02-09

    Forum thread

  • Dependency ansi-to-tui 6.0 is outdated

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

    ansi-to-tui versions

  • Dependency axum 0.7.0 is outdated

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

    axum versions

  • Dependency axum-extra 0.9.2 is outdated

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

    axum-extra versions

  • Dependency cargo-generate =0.21.3 is outdated

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

    cargo-generate versions

  • Dependency cargo_metadata 0.18.1 is outdated

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

    cargo_metadata versions

  • Dependency cargo_toml 0.20.3 is outdated

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

    cargo_toml versions

  • Dependency convert_case 0.6.0 is a bit outdated

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

    convert_case versions

  • Dependency dirs 5.0.1 is outdated

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

    dirs versions

  • Dependency itertools 0.13.0 is outdated

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

    itertools versions

  • Dependency krates 0.17.0 is outdated

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

    krates versions

  • Dependency notify 6.1.1 is outdated

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

    notify versions

  • Dependency strum 0.26.3 is outdated

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

    strum versions

  • Dependency tauri-bundler =2.0.4 is outdated

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

    tauri-bundler versions

  • Dependency thiserror 1.0.40 is a bit outdated

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

    thiserror versions

  • Dependency tower 0.4.13 is outdated

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

    tower versions

  • Dependency tower-http 0.5.2 is outdated

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

    tower-http versions

  • Imprecise dependency requirement walkdir = 2

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

    walkdir versions

  • Missing categories

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

    List of available categories

  • Published crate contains binary files

    The crate contains binary files (JAR file). 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

• kalosm-parse-macro

  • Published crate doesn't match its repository

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

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

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

    Looked for the crate in interfaces/kalosm-parse-macro/. Fetched https://github.com/floneum/floneum.git tagged kalosm-0.4.0 (dbcc4bb9e132d35b069586a9b65922eb794b0d9b).

    Checked on 2025-02-16

    Forum thread

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/floneum/floneum\.git

  • No readme property

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

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

    Use OR instead of /.

    SPDX license list

• dioxus-desktop

  • Dependency cocoa 0.25 is significantly outdated

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

    cocoa versions

  • Dependency infer 0.11.0 is significantly outdated

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

    infer versions

  • Dependency muda 0.11.3 is significantly outdated

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

    muda versions

  • Dependency tokio-tungstenite 0.23.1 is significantly outdated

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

    tokio-tungstenite versions

  • Published crate doesn't match its repository

    Partially verified 43 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in packages/desktop/. Fetched https://github.com/dioxuslabs/dioxus.git tagged v0.6.3 (fc1f1c26f1b5e732c958c83a1665a0a7e5efd205).

    Checked on 2025-02-16

    Forum thread

  • Dependency core-foundation 0.9.3 is a bit outdated

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

    core-foundation versions

  • Dependency global-hotkey 0.5.0 is a bit outdated

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

    global-hotkey versions

  • Dependency rfd 0.14 is outdated

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

    rfd versions

  • Dependency rustc-hash 1.1.0 is a bit outdated

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

    rustc-hash versions

  • Dependency tao 0.30.8 is outdated

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

    tao versions

  • Dependency thiserror 1.0.40 is a bit outdated

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

    thiserror versions

  • Dependency tray-icon 0.19 is a bit outdated

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

    tray-icon versions

  • Dependency webbrowser 0.8.0 is outdated

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

    webbrowser versions

  • Dependency wry 0.45.0 is outdated

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

    wry versions

  • Missing categories

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

    List of available categories

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

    Crate features

• kalosm-language, kalosm-vision, rwuerstchen

  • Dependency image 0.24.7 is outdated

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

    image versions

• manganis-macro

  • Failed to verify create's content against its repository

    Verified 2 out of 11 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 5d4893493b6116d8b39199a6d7028dd287d509da, 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: There is no matching git tag containing version '0.6.2'.
    • 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: workspace dependencies are missing `dunce`.
    • error: Dependencies don't match: 'dunce' uses workspace inheritance, but the root workspace is not available.
      • Make sure to commit and tag after updating Cargo.toml
    • error: Dependencies don't match: 'manganis-core' uses workspace inheritance, but the root workspace is not available.
    • error: Dependencies don't match: 'proc-macro2' uses workspace inheritance, but the root workspace is not available.
    • error: Dependencies don't match: 'quote' uses workspace inheritance, but the root workspace is not available.
    • error: Dependencies don't match: 'syn' uses workspace inheritance, but the root workspace is not available.
    • error: Manifest properties don't match: package.version.
      • If you have a monorepo, you can use git tags in format cratename/v0.6.2

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

    • Cargo.toml.orig does not match the repository.
    • image.png not found.
    • macro/assets/
      • asset.txt exists, but elsewhere in the repo.
      • script.js exists, but elsewhere in the repo.
      • style.css exists, but elsewhere in the repo.
    • src/
      • asset.rs not found.
      • linker.rs not found.
      • lib.rs does not match the repository.

    Looked for the crate in macro/. Fetched https://github.com/dioxuslabs/manganis.git 39ff54d5b337dc8f44d6991c935c5c48631c9043.

    Checked on 2025-01-26

    Forum thread

• kalosm-streams

  • Missing keywords

    Help users find your crates. Add keywords = ["artificial-intelligence", "models", "stream", "kalosm", "pre-trained"] (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.

• rbert, rwhisper, kalosm-llama, rwuerstchen

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

    Crate features

• rbert, rwhisper, kalosm-llama, rwuerstchen

  • Dependency cudarc 0.9.14 is outdated

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

    cudarc versions

• kalosm-learning-macro

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/floneum/floneum\.git

  • No readme property

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

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

    Use OR instead of /.

    SPDX license list

• dioxus_storage

  • Dependency dioxus 0.4 is outdated

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

    dioxus versions

  • Dependency directories 4.0.1 is outdated

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

    directories versions

  • Dependency rustc-hash 1.1.0 is a bit outdated

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

    rustc-hash versions

  • Dependency yazi 0.1.4 is outdated

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

    yazi versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["dioxus", "web", "persistent", "storage", "local"] (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.

• warnings-macro

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/dioxuslabs/warnings\.git

  • No readme property

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

• rmistral

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit 843d33bc2e8e319598a567328c52e587764ff664, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.1.0'.
    • 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: Cargo.toml parse error: Cargo.toml.orig workspace error: the path 'rmistral' does not exist in the given tree; class=Tree (14); code=NotFound (-3).
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.
    • error: Dependencies don't match: 'kalosm-language-model' uses different versions: '0.1.0' vs '0.2.1'.
      • Make sure to commit and tag after updating Cargo.toml
    • error: Dependencies don't match: 'kalosm-sample' uses different versions: '0.1.0' vs '0.2.1'.
    • error: Dependencies don't match: 'kalosm-streams' uses different versions: '0.1.0' vs '0.2.1'.
    • warning: Repository fetch error: missing delta bases; class=Indexer (15).

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

    • Cargo.toml not found.
    • Cargo.lock not found.
    • infer.rs not found.
    • src/
      • source.rs not found.
      • model.rs not found.
      • language_model.rs not found.
      • raw.rs not found.
      • lib.rs not found.

    Looked for the crate in models/rmistral/. Fetched https://github.com/floneum/floneum.git f929d865d96f75f66438df465f6965b30a217d0d.

    Checked on 2024-07-28

    Forum thread

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/floneum/floneum\.git

  • Dependency candle-core 0.3.1 is significantly outdated

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

    candle-core versions

  • Dependency candle-nn 0.3.1 is significantly outdated

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

    candle-nn versions

  • Dependency kalosm-language-model 0.1.0 is significantly outdated

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

    kalosm-language-model versions

  • Dependency kalosm-sample 0.1.0 is significantly outdated

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

    kalosm-sample versions

  • Dependency tokenizers 0.13.4 is significantly outdated

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

    tokenizers versions

  • Locked dependency version llm-samplers =0.0.7

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    llm-samplers versions

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

  • Dependency candle-transformers 0.3.1 is significantly outdated

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

    candle-transformers versions

  • Dependency cudarc 0.9.14 is outdated

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

    cudarc versions

  • Dependency hf-hub 0.3.0 is a bit outdated

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

    hf-hub versions

  • Dependency kalosm-streams 0.1.0 is outdated

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

    kalosm-streams versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

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

    Use OR instead of /.

    SPDX license list

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["mistral", "machine", "models", "interface", "candle"] (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 'cudarc' 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 'cudarc' may have been unintentional.

    Crate features

• blitz

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/jkelleyrtp/blitz\.git

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

No issues found in: sledgehammer_bindgen sledgehammer_bindgen_macro sledgehammer

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