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.

• sdc_apis

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit 3fc8c7f8bb3f97bf109e94c9907b471afbcf233b, 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: 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.toml.orig does not match the repository.
    • secretflowapis/v1/
      • common.proto does not match the repository.
      • status.proto does not match the repository.
    • secretflowapis/v1/sdc/
      • digital_envelope.proto does not match the repository.
      • core.proto does not match the repository.
    • auth_manager.proto does not match the repository.
    • data_agent.proto does not match the repository.
    • tee_task_params.proto does not match the repository.
    • secretflowapis/v1/sdc/teeapps/params/
      • table_statistics_params.proto not found.
      • lr_hyper_params.proto not found.
      • biclassifier_evaluation.proto not found.
      • .OPENSOURCE-CLEANUP-RMDIR not found.
      • predict.proto not found.
      • dataset_split.proto not found.
      • sql_process.proto not found.
      • stats_corr_params.proto not found.
      • sql_analysis.proto not found.
      • xgb_hyper_params.proto not found.
      • vif_params.proto not found.
      • dataset_sample.proto not found.
      • woe_binning.proto not found.
      • dataset_filter.proto not found.
    • secretflowapis/v2/
      • status.proto does not match the repository.
      • common.proto does not match the repository.
    • capsule_manager.proto does not match the repository.
    • data_capsule_proxy.proto not found.
    • ra_proxy.proto not found.

    Fetched https://github.com/secretflow/secure-data-capsule-apis.git 54b2e064f92c2c12a20b871f65a8a4ed26109841.

    Checked on 2024-11-20

    This check is experimental.

    Forum thread

  • Dependency prost-wkt 0.4 is significantly outdated

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

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

    prost-wkt versions

  • Dependency prost-wkt-build 0.4 is significantly outdated

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

    prost-wkt-build versions

  • Dependency prost-wkt-types 0.4 is significantly outdated

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

    prost-wkt-types versions

  • Dependency tonic 0.9.2 is significantly outdated

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

    tonic versions

  • Dependency prost 0.11 is outdated

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

    prost versions

  • Dependency prost-types 0.11.1 is outdated

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

    prost-types versions

  • Dependency tonic-build 0.9.2 is outdated

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

    tonic-build versions

  • Missing keywords

    Help users find your crates. Add keywords = ["api", "secret-flow", "capsule", "proto", "generated"] (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.

• trustedflow-attestation-rs

  • Failed to verify create's content against its repository

    Verified 1 out of 7 files (includes 0 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • 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.1.2-dev240313'.
    • 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: package.build: crates.io=build.rs, orig=<unset>.

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

    • build.rs not found.
    • Cargo.toml.orig does not match the repository.
    • .OPENSOURCE-CLEANUP-RMDIR exists, but elsewhere in the repo.
    • lib.rs does not match the repository.
    • tdx_report.json not found.

    Looked for the crate in cargo/trustedflow-attestation-rs/. Fetched https://github.com/secretflow/trustedflow.git 47d96c25b320d6c2faae3332aed4d1b83b6b9872.

    Checked on 2024-07-24

    Forum thread

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/secretflow/trustedflow\.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.

  • 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 sdc_apis 0.2.1-dev20240222 is outdated

    Consider upgrading to 0.3.0-hyper-dev20241119 to get all the fixes and improvements.

    sdc_apis versions

  • Latest prerelease is old

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

  • Missing keywords

    Help users find your crates. Add keywords = ["confidential-computing", "attestation", "privacy-preserving", "tee", "system"] (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.

• trustedflow-attestation-sys

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • 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.1.1-dev240313'.
    • 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.toml.orig does not match the repository.
    • bindings.rs not found.

    Looked for the crate in cargo/trustedflow-attestation-sys/. Fetched https://github.com/secretflow/trustedflow.git 3d137b890e0863ed55581b286612cdc06c95ed93.

    Checked on 2024-07-24

    Forum thread

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/secretflow/trustedflow\.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.

  • 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

  • Latest prerelease is old

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

    Help users find your crates. Add keywords = ["confidential-computing", "privacy-preserving", "attestation", "tee", "trustedflow"] (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.

• trustedflow-attestation-rs, sdc_apis, trustedflow-attestation-sys

  • Missing categories

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

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