← Home

@bazel/runfiles

Node.js runfiles helpers for Bazel

45
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

google-wombotalexeaglebazel-managergmags

Keywords

bazelrunfilesrunfiles helpers

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in runfiles.js is the documented Bazel runfiles patch mechanism, loading a path derived from Bazel environment variables. This is intentional and stable for this package. ai
bogus-package bogus-package AI (bogus-package): No npm deps is expected for a Bazel integration utility; sparse README is a documentation style choice, not a spam indicator for this established package. ai

Versions (showing 45 of 45)

Version Deps Published
6.5.0 0 / 0
6.3.1 0 / 0
6.3.0 0 / 0
5.8.1 0 / 0
5.7.3 0 / 0
5.7.2 0 / 0
5.7.1 0 / 0
5.7.0 0 / 0
5.6.0 0 / 0
5.5.4 0 / 0
5.5.3 0 / 0
5.5.2 0 / 0
5.5.1 0 / 0
5.5.0 0 / 0
5.4.2 0 / 0
5.4.1 0 / 0
5.4.0 0 / 0
5.3.1 0 / 0
5.3.0 0 / 0
5.2.0 0 / 0
5.1.0 0 / 0
5.0.2 0 / 0
5.0.1 0 / 0
5.0.0 0 / 0
4.6.2 0 / 0
4.6.1 0 / 0
4.6.0 0 / 0
4.5.0 0 / 0
4.4.6 0 / 0
4.4.5 0 / 0
4.4.2 0 / 0
4.4.0 0 / 0
4.3.0 0 / 0
4.2.0 0 / 0
4.1.0 0 / 0
4.0.0 0 / 0
3.8.0 0 / 0
3.7.0 0 / 0
3.6.0 0 / 0
3.5.1 0 / 0
3.5.0 0 / 0
3.4.2 0 / 0
3.4.1 0 / 0
3.4.0 0 / 0
3.3.0 0 / 0

v4.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.