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.

• fimdoc

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["text-processing", "mathematics"] to the Cargo.toml.

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["fimdoc", "bbcode", "document", "obsidian-vault", "fiction"] (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.

• trot

  • 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 be3d5cd6670faf20028ba37ead33f7307d16269e, 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.1.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: can't load root workspace.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: Can't find workspace in //...
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

    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.
    • lib.rs does not match the repository.

    Fetched https://github.com/silkrose/rarity.git 1bb21dfc0084ed27ffc97af323784ee8650100b8.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

• trot, rainbow-dash, rarity, fimd

  • Missing categories

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

    List of available categories

• rainbow-dash

  • 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: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: can't load root workspace.
    • error: Cargo.toml parse error: Cargo.toml.orig workspace error: Can't find workspace in //...
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

    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.
    • lib.rs does not match the repository.

    Fetched https://github.com/silkrose/rarity.git e13b98f45af437214e53817dd89c2a8556292859.

    Checked on 2024-07-28

    Forum thread

• applejack

  • No repository property

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

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

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

    List of available categories

  • Missing keywords

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

• twilight-sparkle

  • Dependency serde_yaml 0.8.21 has issues

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

    serde_yaml crate

  • Dependency clap 2.33.3 is outdated

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

    clap versions

  • Dependency env_logger 0.9.0 is outdated

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

    env_logger versions

  • Dependency nom 7.0.0 is a bit outdated

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

    nom versions

  • Dependency toml 0.5.8 is outdated

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

    toml versions

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

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["twilight-sparkle", "twilight", "sparkle", "help", "subcommand"] (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.

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

• rarity

  • Imprecise dependency requirement serde = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as serde = "1.0.219". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    serde versions

  • Dependency fancy-regex 0.13.0 is outdated

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

    fancy-regex versions

  • Missing keywords

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

• fimd

  • Published crate doesn't match its repository

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

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

    • Cargo.lock exists, but elsewhere in the repo.

    Looked for the crate in rs/. Fetched https://github.com/meadowsys/fimd.git edc00e45737cda1289ade89f204442633bf614f1.

    Checked on 2024-08-05

    Forum thread

  • Dependency hashbrown 0.14.3 is significantly outdated

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

    hashbrown versions

  • Missing keywords

    Help users find your crates. Add keywords = ["fimd", "bb-code", "remark-fimd", "txt", "md"] (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.

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

• fanfic-macros

  • Internal error

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

• fanfic

  • Internal error

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

• fluttershy

  • Internal error

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

• mare

  • Internal error

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

No issues found in: fim mlp nopony scootaloo sweetie-belle pinkie-pie golden-oak-library pony

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