遵循以下最佳实践的项目将能够自愿的自我认证,并显示他们已经实现了核心基础设施计划(OpenSSF)徽章。 显示详细资料
[](https://www.bestpractices.dev/projects/8050)
<a href="https://www.bestpractices.dev/projects/8050"><img src="https://www.bestpractices.dev/projects/8050/badge"></a>
An extremely fast RBE-compatible cache and remote executor.
The project is maintained by multiple core contributors https://github.com/TraceMachina/nativelink/graphs/contributors.
Nativelink requires all source code files to produce a copyright header at the top of each file. Example: https://github.com/TraceMachina/nativelink/blob/main/nativelink-scheduler/src/action_scheduler.rs
Repository on GitHub, which uses git. git is distributed.
Nativelink uses the label good-first-issue in github for small tasks.
good-first-issue
https://github.com/TraceMachina/nativelink/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
Anyone within the organization is required to have 2FA enabled on their github account.
https://github.com/TraceMachina/nativelink/blob/main/CONTRIBUTING.md#creating-pull-requests
Nativelink uses nix for official builds: https://github.com/TraceMachina/nativelink/blob/main/SECURITY.md#using-oci-images
You can use Bazel or Cargo to run the testsuite. See https://github.com/TraceMachina/nativelink/tree/main/.github/workflows for invocation examples.
The project uses GitHub actions. You can review the current CI at https://github.com/TraceMachina/nativelink/tree/main/.github/workflows.
NativeLink uses TLS encryption by default.
// X-Content-Type-Options was not set to "nosniff".
The project does not yet use fuzzing. It is planned to add fuzzing in the future. At the moment there would be limited use for it as the project does not yet have branch based coverage.
Fuzzing is not yet implemented. Tests are deliberately designed to run over the public API of the internal libraries. Clippy is quite strict and enabled during test builds, covering a lot of what assertions in other languages would cover.
后退