@bazel/runfiles

Release historycaution

The package has 52 releases since 2021 with a typical interval of about 13 days, but no registry release in the last 12 months despite the repository being updated recently. This suggests the published package may be lagging behind project activity.

Repo bus factorcaution

All five recent commits came from one contributor, leaving maintenance dependent on a single active person. Organization backing provides some capacity for handoff, but no second recent contributor is shown.

Repo commit activitycaution

The repository recorded five commits in the last three months, so activity has not stopped, but the volume is modest for a foundational package.

Repo package mentioncaution

The repository name does not match the package and its README does not mention @bazel/runfiles, so the package-to-source relationship is not explicit. The mismatch may be normal for a monorepo subpackage, but the missing README mention leaves a genuine traceability gap.

Repo toolingcaution

The collected repository profile reports no build-tool or security-scanning tools. Because the repository clearly contains Bazel and CI configuration, this is a limited transparency gap rather than evidence of absent project tooling.