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.
number-theory
Failed to verify create's content against its repository
Verified 14 out of 29 files (includes 2 Cargo-generated).
- warning: The crates.io package has no commit hash associated with it.
- Publish a new version, without using
--allow-dirtyflag. Make sure all changes are committed before publishing. Useinclude/excludeinCargo.tomlto omit unnecessary files.
- Publish a new version, without using
- warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
- warning: There is no matching git tag containing version '0.0.25'.
- warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
Files in the crates.io crate compared to the repository:
Cargo.lockdoes not match the repository.README.mddoes not match the repository.Cargo.toml.origdoes not match the repository.src/lib.rsdoes not match the repository.structs.rsdoes not match the repository.result.rsdoes not match the repository.ntrait.rsdoes not match the repository.
src/arithmetic/mpz_prime.rsdoes not match the repository.mpz_ent.rsdoes not match the repository.
src/primitive/promotion.rsdoes not match the repository.fourbytes.rsdoes not match the repository.sixteenbytes.rsdoes not match the repository.montprim.rsdoes not match the repository.eightbytes.rsdoes not match the repository.sieve.rsdoes not match the repository.signednt.rsdoes not match the repository.
Fetched
https://github.com/jasory/ent.git9a1c81ddd095d73412213b63cc7c7c6b44eeec4a.Checked on 2025-03-09
This check is experimental.
- warning: The crates.io package has no commit hash associated with it.
machine-factor
Failed to verify create's content against its repository
Verified 5 out of 10 files (includes 3 Cargo-generated).
- warning: The crates.io package has no information about its path inside its repository.
- 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).
- warning: There is no matching git tag containing version '0.2.4'.
git tag v0.2.4 c5533f3f6b14cc52056fc13504763d536abed2dc; git push origin --tags
Files in the crates.io crate compared to the repository:
Cargo.locknot found.Cargo.toml.origdoes not match the repository.src/lib.rsdoes not match the repository.wfactor.rsdoes not match the repository.mfactor.rsdoes not match the repository.primes.rsdoes not match the repository.
Fetched
https://github.com/jasory/machine-factor.gitc5533f3f6b14cc52056fc13504763d536abed2dc.Checked on 2025-04-28
number-theory, nuclide, c-prime, ssmr, pion, nt-primes, sirp
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.
c-prime
Failed to verify create's content against its repository
Verified 4 out of 9 files (includes 1 Cargo-generated).
- warning: The crates.io package has no commit hash associated with it.
- Publish a new version, without using
--allow-dirtyflag. Make sure all changes are committed before publishing. Useinclude/excludeinCargo.tomlto omit unnecessary files.
- Publish a new version, without using
- warning: The crates.io package has no information about its path inside its repository.
- warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
- warning: Could not discover crate's location in its repository (via tags).
- 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.
Files in the crates.io crate compared to the repository:
README.mddoes not match the repository.Cargo.toml.origdoes not match the repository.src/lib.rsdoes not match the repository.func.rsdoes not match the repository.iterators.rsdoes not match the repository.
Fetched
https://github.com/jasory/c-prime.gitaa9b5f8275714c02a21b5ccba7f266d5bff34c26.Checked on 2025-01-12
- warning: The crates.io package has no commit hash associated with it.
nuclide
Failed to verify create's content against its repository
Verified 31 out of 35 files (includes 2 Cargo-generated).
- warning: The crates.io package has no commit hash associated with it.
- Publish a new version, without using
--allow-dirtyflag. Make sure all changes are committed before publishing. Useinclude/excludeinCargo.tomlto omit unnecessary files.
- Publish a new version, without using
- warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
- warning: There is no matching git tag containing version '0.3.0'.
- warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
Files in the crates.io crate compared to the repository:
Cargo.lockdoes not match the repository.Cargo.toml.origdoes not match the repository.README.mdexists, but elsewhere in the repo.standard_atomic_mass.rsdoes not match the repository.element.rsdoes not match the repository.
Looked for the crate in
Nuclide/. Fetchedhttps://github.com/jasory/iridium.git78920cec30879d13bedb1029a75a2e9ebf1588ec.Checked on 2024-08-04
- warning: The crates.io package has no commit hash associated with it.
ssmr
Latest stable release is old
It's been over 16 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").Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.
Failed to verify create's content against its repository
Verified 9 out of 10 files (includes 2 Cargo-generated).
- warning: The crates.io package has no commit hash associated with it.
- Publish a new version, without using
--allow-dirtyflag. Make sure all changes are committed before publishing. Useinclude/excludeinCargo.tomlto omit unnecessary files.
- Publish a new version, without using
- warning: The crates.io package has no information about its path inside its repository.
- warning: There is no matching git tag containing version '1.0.0'.
- warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
Files in the crates.io crate compared to the repository:
Cargo.locknot found.README.mddoes not match the repository.
Fetched
https://github.com/jasory/ssmr.git7cac06200c03bdd39ee3b3fa52aaa7d7069d803a.Checked on 2024-07-28
- warning: The crates.io package has no commit hash associated with it.
sirp
Dependency number-theory 0.0.1 is outdated
Consider upgrading to 0.0.25 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
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?
nt-primes
Dependency number-theory 0.0.24 is outdated
Consider upgrading to 0.0.25 to get all the fixes and improvements.
No issues found in: machine-prime
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance] to their
status = "deprecated"Cargo.toml.