> ## Documentation Index
> Fetch the complete documentation index at: https://aspect.build/llms.txt
> Use this file to discover all available pages before exploring further.

# Aspect's rulesets are moving to bazel-contrib, starting with rules_lint

> Aspect is donating its Bazel rulesets to bazel-contrib, starting with rules_lint. What changes when you upgrade, and what's next for rules_js and rules_py.

# Aspect's rulesets are moving to bazel-contrib, starting with rules\_lint

Greg Magolan

***

![](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/blog/stock/handshake.jpg)

rules\_lint now lives at [github.com/bazel-contrib/rules\_lint](https://github.com/bazel-contrib/rules_lint). The Bazel Rules Authors SIG [approved the donation](https://github.com/bazel-contrib/SIG-rules-authors/issues/129) on November 10, and Alex Eagle, who wrote the first version, is its primary maintainer. It's the first Aspect ruleset to move. rules\_js, rules\_aws, and rules\_buildx will follow.

If you rely on rules\_lint today, here's the short version: nothing breaks, and Aspect remains a maintainer. Community governance adds maintainers. It doesn't remove ours.

## What changes for you

Every `aspect_rules_lint` release stays on the Bazel Central Registry, builds pinned to one keep working, and the old `aspect-build/rules_lint` URLs redirect to the new repository.

The first release out of bazel-contrib is still in progress. It will be a major release, 3.0.0, published to the BCR as `rules_lint`, and the `aspect_` prefix is already gone on `main`. Until it ships, stay on `aspect_rules_lint`.

To upgrade once the 3.0.0 release ships, drop the `aspect_` prefix in your `bazel_dep`, `load()` statements, and flags:

```starlark theme={null}
# MODULE.bazel
bazel_dep(name = "rules_lint", version = "3.0.0")
```

The Rust and Scala modules are now `rules_lint_rust` and `rules_lint_scala`. Upgrade all three together. `aspect_rules_lint` and `rules_lint` are different modules to Bazel, so a graph that has both gets two copies instead of one resolved version.

To change only the dependency line, keep the old repository name:

```starlark theme={null}
bazel_dep(name = "rules_lint", version = "3.0.0", repo_name = "aspect_rules_lint")
```

Your existing `load()` labels and `--@aspect_rules_lint//lint:fix` flags keep working. This covers your root module only, so a dependency still on `aspect_rules_lint` brings in the second copy.

The Aspect CLI has first-class support for rules\_lint through its [`lint`](https://aspect.build/docs/cli/tasks/lint) and [`format`](https://aspect.build/docs/cli/tasks/format) tasks. If you use `aspect lint --fix` and renamed the repository, point the Aspect CLI at the new flag in `.aspect/config.axl` (Aspect CLI [v2026.45.6](https://github.com/aspect-build/aspect-cli/releases/tag/v2026.45.6) or later):

```python theme={null}
ctx.tasks["lint"].args.rules_lint_fix_flag = "@rules_lint//lint:fix"
```

A future Aspect CLI release will make `@rules_lint//lint:fix` the default, and you can remove the line then.

Want a hand with the upgrade? Aspect Enterprise customers can reach out through their usual support channel, and we'll walk through it with you.

## Why bazel-contrib

Nearly 100 people have contributed to rules\_lint, and it covers about 30 languages. A ruleset that much of the community builds on belongs in a community-owned home.

bazel-contrib is that home: a GitHub org owned by the Bazel community, with shared CI and release infrastructure, where maintainers can come from any company.

Thank you to everyone who filed an issue, sent a fix, or added a linter. You built this. Thanks also to the Rules Authors SIG for reviewing the donation. And to our customers, whose real-world builds and feedback shaped rules\_lint into what it is today, thank you.

## Maintainers

Alex Eagle co-founded Aspect and wrote the first version of rules\_lint. He now works on it independently of Aspect, as its primary maintainer. Nobody knows the codebase or its design tradeoffs better. His [BazelCon 2024 talk on rules\_lint](https://www.youtube.com/watch?v=CnK-RAdfrpI) is still the best introduction to how it works and why. Thank you, Alex, for building it and for coming back to lead it.

Aspect stays on as a maintainer alongside him. We run rules\_lint in our own repositories, and our customers run it in theirs.

## Next up: rules\_js, rules\_aws, and rules\_buildx

We're working to donate every ruleset Aspect has built: rules\_js and the rest of the JavaScript family (rules\_ts, rules\_swc, rules\_jest, rules\_esbuild, and friends), rules\_aws, and rules\_buildx. Their use has spread well past Aspect and our customers, and they're ready for maintainers from across the community.

Each move works the way this one did. The ruleset drops the `aspect_` prefix from its BCR name (`rules_aws` already has, and `rules_js` does from 4.0), the rename lands only in a new major release with upgrade steps in its notes, and existing releases stay on the BCR. We'll announce each donation once the SIG approves it.

rules\_py takes a different path. We're working with Google and the rules\_python maintainers toward merging rules\_py and rules\_python, so the Bazel community gets one Python ruleset that covers what both do today. Nothing changes for rules\_py users today. rules\_py 2.0 ships by the end of November, we'll keep maintaining rules\_py while the merge work happens, and we'll share migration guidance well before anything changes.

Keeping these rulesets healthy is core to our work as Aspect puts its focus on [Aspect Workflows](https://aspect.build/docs/aspect-workflows/platform/overview.md), because our own builds and our customers' builds run on them. We believe the best home for a widely used ruleset is a community one, and that's good for our customers too: more maintainers, faster reviews, more eyes on each release, and fixes from the people who hit the bugs.

## Get involved

Find the maintainers and other rules\_lint users in #linting-and-formatting on the [Bazel Slack](https://slack.bazel.build). Thanks to Chuck Grindel for setting up the channel.

Report rules\_lint issues on GitHub. Aspect Enterprise customers can keep reaching us through their usual support channel, for rules\_lint and every other ruleset.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.