eclipse-score/score

Repository dependency audit: Identify Rust crates usage across repositories

Open

#1,839 opened on Oct 2, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Starlark (102 forks)auto 404
good first issue

Repository metrics

Stars
 (99 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

We need to perform a dependency audit across all repositories to determine which ones use Rust and document the specific crates they depend on.

This task includes:

  1. Iterating through all repositories in the S-Core organization.
  2. Identifying which repositories contain Rust projects (presence of Cargo.toml).
  3. Extracting the list of crates used from Cargo.toml and/or Cargo.lock.
  4. Creating a consolidated report with the following information:
    • Repository name
    • Path to Rust project(s) (if multiple)
    • List of crates in use (with versions if available)

This is particularly important for the new source-of-truth repo introduced by Mark, but should be applied to all Rust-based repositories.

The report should be stored centrally.

Contributor guide

Research direction
Iterate through repositories in the S Core organization, look for Cargo.toml files, extract crate dependencies, and compile a report.
Tech stack
rustshell
Domain
devopstooling
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust (basic)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40