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.
dynamic-html
README missing from the repository
We've searched
https://github\.com/densky\-framework/dynamic\-html\.git
and could not find a README file there.Dependency wasm-bindgen =0.2.81 is significantly outdated
Upgrade to 0.2.100 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.
Locked dependency version wasm-bindgen =0.2.81
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.
Published crate doesn't match its repository
Partially verified 15 files (includes 3 Cargo-generated).
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.
Fetched
https://github.com/densky-framework/dynamic-html.git
5e9c2569b7a8d3dafcc55f8b10017a101d908801.Checked on 2024-08-10
This check is experimental.
Missing keywords
Help users find your crates. Add
keywords = ["dynamic-html", "typescript", "html", "optimization"]
(up to 5) to theCargo.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.
densky
Failed to verify create's content against its repository
Verified 3 out of 13 files (includes 3 Cargo-generated).
- warning: Crate tarball has been published from the commit c22482a62cf4b5e96b01408cebe8758ee82760ff, which is not in the repository.
- Create git tags after comitting any changes, and commit changes after bumping versions and running
cargo update
.
- Create git tags after comitting any changes, and commit changes after bumping versions and running
- 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=false; orig=true.
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.Cargo.toml.orig
does not match the repository.src/
progress.rs
not found.compiler.rs
not found.main.rs
does not match the repository.
src/commands/
build.rs
not found.dev.rs
not found.mod.rs
not found.
src/watcher/
mod.rs
not found.poll.rs
not found.utils.rs
not found.
Fetched
https://github.com/densky-framework/core.git
87f7b3866dff6a77677439bcf5ec1665e59e3123.Checked on 2024-07-28
- warning: Crate tarball has been published from the commit c22482a62cf4b5e96b01408cebe8758ee82760ff, which is not in the repository.
README missing from the repository
We've searched
https://github\.com/densky\-framework/core\.git
and could not find a README file there.Dependency recv-dir 0.2.0 is slightly outdated
Consider upgrading to 0.3.1 to get all the fixes and improvements.
Dependency ureq 2.6.2 is a bit outdated
Consider upgrading to 3.0.11 to get all the fixes and improvements.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.Missing keywords
Help users find your crates. Add
keywords = ["densky", "deno"]
(up to 5) to theCargo.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.
amvm
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.Published crate doesn't match its repository
Partially verified 49 files (includes 2 Cargo-generated).
Fetched
https://github.com/brayan-724/amvm.git
faef307c6fe7f6311a9bedff58847b222ac19290.Checked on 2024-08-10
Missing keywords
Help users find your crates. Add
keywords = ["amvm", "lenguage", "bytecode", "variables", "machine"]
(up to 5) to theCargo.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.
amvm, dynamic-html, densky, densky-core
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.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.
densky-core
README missing from the repository
We've searched
https://github\.com/densky\-framework/core\.git
and could not find a README file there.Published crate doesn't match its repository
Partially verified 27 files (includes 3 Cargo-generated).
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.
Fetched
https://github.com/densky-framework/core.git
330fb704847e259e73d01ba4902d2a6f81624ee9.Checked on 2024-08-10
Dependency colored 2 is a bit outdated
Consider upgrading to 3.0.0 to get all the fixes and improvements.
Missing keywords
Help users find your crates. Add
keywords = ["framework", "tree", "container"]
(up to 5) to theCargo.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.
dynamic-html, densky, densky-core
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.