stalecrate 0.1.0__tar.gz

stalecrate-0.1.0/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.egg-info/
+dist/
+.venv/
+
+# experiment scratch: crate sources, rustdoc JSON, compiler output (several GB)
+work/
+
+# benchmark build caches and per-run outputs
+bench/.target*
+bench/.build*
+bench/runs/
+bench/reference/
+bench/smoke/target/
+bench/*.log

stalecrate-0.1.0/LICENSE-APACHE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

stalecrate-0.1.0/LICENSE-MIT

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mohib Shaikh
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

stalecrate-0.1.0/PKG-INFO

@@ -0,0 +1,101 @@
+Metadata-Version: 2.5
+Name: stalecrate
+Version: 0.1.0
+Summary: Tell your coding agent which Rust crates changed after its training cutoff
+Project-URL: Repository, https://github.com/MohibShaikh/stalecrate
+Project-URL: Issues, https://github.com/MohibShaikh/stalecrate/issues
+Author-email: Mohib Shaikh <mohibuddin9@gmail.com>
+License-Expression: MIT OR Apache-2.0
+License-File: LICENSE-APACHE
+License-File: LICENSE-MIT
+Keywords: cargo,claude-code,coding-agent,llm,rust
+Classifier: Environment :: Console
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+# stalecrate
+
+Tell your coding agent which Rust crates changed after its training cutoff, and what changed.
+
+Claude Opus 5.5 learned Rust from data that stops in June 2026. Bevy 0.19 shipped on June 19 and 0.20 on October 8. Ask Opus for a Bevy 0.20 observer and it writes `On<Add, Health>`. That form stopped compiling in 0.20, where the component moved into the event: `On<Add<Health>>`.
+
+stalecrate reads your `Cargo.lock`, finds the dependencies released after the model's cutoff, and diffs their public APIs between the version the model knows and the version you pin. It then checks which of the changed items your code uses and writes short notes into `CLAUDE.md` or `AGENTS.md`. Each note quotes the crate's own migration guide where one exists.
+
+## Usage
+
+```sh
+rustup toolchain install nightly   # rustdoc JSON is nightly-only
+uvx stalecrate scan --model claude-opus-5-5
+uvx stalecrate sync --model claude-opus-5-5
+```
+
+`scan` lists the dependencies with releases after the cutoff. `sync` builds the API diffs and writes the notes between `<!-- stalecrate:begin -->` and `<!-- stalecrate:end -->`, leaving the rest of the file alone. It writes to `CLAUDE.md` if the project has one and `AGENTS.md` otherwise, or to `--file`. `stalecrate status` exits 1 when the notes no longer match `Cargo.lock`, so you can run it in CI or a pre-commit hook.
+
+The only cutoff built in is Claude Opus 5.5 (June 2026), because it's the only one I could confirm. For any other model pass `--cutoff YYYY-MM`. Releases from the 30 days before the cutoff count as unknown, since the training data covers them thinly. Change that with `--margin-days`.
+
+## What a note looks like
+
+From a project with Bevy 0.18 examples bumped to 0.20.1:
+
+```markdown
+#### Moved Observer events `B` Bundle generic into the event type
+(bevy 0.20 migration guide; your code uses `Add`, `On` in 3 files)
+
+The `B: Bundle` type parameter has been removed from `On<E, B>` in observer systems.
+...
+- `TextFont::font_size` changed: `font_size: f32` → `font_size: FontSize` (used in 3 files)
+- `PointLight::shadows_enabled` was removed in bevy_light 0.20.1; `PointLight` gained: `contact_shadows_enabled`, `shadow_maps_enabled` (used in 1 files)
+```
+
+Sections are ranked by how many of your files they touch and cut to a token budget (`--max-tokens`, default 4000).
+
+## Does it help?
+
+I measured this on 12 Bevy 0.20 tasks with `claude-opus-5-5`. They covered observers, component hooks, picking, UI buttons, text, glTF scenes, lights, bloom and a few others. Every task has an official Bevy 0.20 example that compiles with the same feature set, so each one is solvable. A run passes when `cargo check` succeeds and the code contains what the task asked for. The two conditions differ only in the system prompt. Control gets one line saying the project pins Bevy 0.20.1. The notes condition gets that line plus a 4,000-token notes file, frozen before the first run.
+
+Writing `main.rs` in one reply, with no tools and 5 samples per task:
+
+| | control | with notes |
+|---|---|---|
+| compiles | 31/60 (52%) | 55/60 (92%) |
+| mean compiler errors | 2.4 | 0.1 |
+| deprecation warnings | 25 | 0 |
+| cost per call | $0.036 | $0.090 |
+
+As an agent that can run `cargo check` and fix its own errors, with 3 samples per task:
+
+| | control | with notes |
+|---|---|---|
+| compiles | 36/36 | 36/36 |
+| median turns | 6 | 3 |
+| median wall time | 38s | 25s |
+| cost per session | $0.112 | $0.139 |
+
+With a compiler in the loop Opus gets there either way, by reading the errors. The notes halve the turns. On tasks this small they also make each session about 24% more expensive, because the notes ride along in every prompt. Wall times are rough, since two sessions shared the CPU.
+
+The one task the notes didn't fix was loading a glTF scene (0/5 in both conditions). The migration guide renames `SceneRoot` to `WorldAssetRoot` in a list that the excerpt cut off. The current version always keeps guide lines that name an item your code uses. I haven't rerun the benchmark since that fix, because tuning on the test set would inflate the number.
+
+I also checked the API diff itself against the compiler. I took Bevy 0.18 examples, compiled them against 0.20.1, and asked whether the diff had flagged what broke. On 20 examples held out from all tuning, it flagged all 8 that broke. 19 of their 25 compiler errors (76%) name an item the diff flagged. Only 16 of the 42 items it predicted would break showed up in an error. That 38% is a lower bound, since rustc stops reporting some errors once others appear.
+
+Everything to rerun this is in the repo. The tasks are in `bench/tasks.json`, the frozen notes in `bench/notes.md`, the runner in `scripts/bench.py`, and per-run results in `bench/results-*.json`.
+
+## How it works
+
+1. **Find what's new.** For every package in `Cargo.lock` that you depend on, or that extends a name you depend on (`bevy_ecs` for `bevy`), it asks crates.io for release dates. The newest release from before the cutoff is the version the model knows. A `0.0.x` upload made long before the real releases counts as a name reservation, so that crate is treated as new.
+2. **Diff the APIs.** It builds rustdoc JSON for both versions in a throwaway package and caches it in `~/.cache/stalecrate`. Then it walks the public items, including methods, fields and enum variants. An item that disappears from one crate and shows up in a crate that's new in this version counts as moved. Changes that only touch trait bounds or lifetime names get dropped, because they rarely break callers.
+3. **Find what you use.** It runs a text scan of your `.rs` files with comments stripped. A removed name that still exists in another crate (`render_graph::Node` vs `bevy_ui::Node`) only counts when you write the qualified path. This step is an estimate, not name resolution.
+4. **Explain it.** It looks for migration guides shipped inside the crate (Bevy ships `_release-content/migration-guides`), `MIGRATION.md`/`UPGRADING.md`, and changelog entries for the versions in range. If the crate ships none of those, it uses GitHub release notes, and `GITHUB_TOKEN` raises the rate limit. Each used item links to the section that names it. Anything left over gets a one-line note with the old and new signature.
+
+## Limits
+
+- Building rustdoc JSON needs a nightly toolchain, and the JSON format changes between nightlies. I tested with format version 61 (nightly 2026-10-06).
+- Building docs runs build scripts, so crates that need missing system libraries get skipped. On the test machine that meant `bevy_audio` and `bevy_dev_tools` (ALSA) and `bevy_gilrs` (udev).
+- The first `sync` on a dependency tree the size of Bevy took 12 minutes. Later runs use the cache.
+- Usage matching is textual, so a type you shadow with your own of the same name can still match.
+- The benchmark covers one model and one crate family. I haven't measured crates that ship no migration guide, such as egui or wgpu.
+
+## License
+
+MIT or Apache-2.0, at your option.

stalecrate-0.1.0/README.md

@@ -0,0 +1,84 @@
+# stalecrate
+
+Tell your coding agent which Rust crates changed after its training cutoff, and what changed.
+
+Claude Opus 5.5 learned Rust from data that stops in June 2026. Bevy 0.19 shipped on June 19 and 0.20 on October 8. Ask Opus for a Bevy 0.20 observer and it writes `On<Add, Health>`. That form stopped compiling in 0.20, where the component moved into the event: `On<Add<Health>>`.
+
+stalecrate reads your `Cargo.lock`, finds the dependencies released after the model's cutoff, and diffs their public APIs between the version the model knows and the version you pin. It then checks which of the changed items your code uses and writes short notes into `CLAUDE.md` or `AGENTS.md`. Each note quotes the crate's own migration guide where one exists.
+
+## Usage
+
+```sh
+rustup toolchain install nightly   # rustdoc JSON is nightly-only
+uvx stalecrate scan --model claude-opus-5-5
+uvx stalecrate sync --model claude-opus-5-5
+```
+
+`scan` lists the dependencies with releases after the cutoff. `sync` builds the API diffs and writes the notes between `<!-- stalecrate:begin -->` and `<!-- stalecrate:end -->`, leaving the rest of the file alone. It writes to `CLAUDE.md` if the project has one and `AGENTS.md` otherwise, or to `--file`. `stalecrate status` exits 1 when the notes no longer match `Cargo.lock`, so you can run it in CI or a pre-commit hook.
+
+The only cutoff built in is Claude Opus 5.5 (June 2026), because it's the only one I could confirm. For any other model pass `--cutoff YYYY-MM`. Releases from the 30 days before the cutoff count as unknown, since the training data covers them thinly. Change that with `--margin-days`.
+
+## What a note looks like
+
+From a project with Bevy 0.18 examples bumped to 0.20.1:
+
+```markdown
+#### Moved Observer events `B` Bundle generic into the event type
+(bevy 0.20 migration guide; your code uses `Add`, `On` in 3 files)
+
+The `B: Bundle` type parameter has been removed from `On<E, B>` in observer systems.
+...
+- `TextFont::font_size` changed: `font_size: f32` → `font_size: FontSize` (used in 3 files)
+- `PointLight::shadows_enabled` was removed in bevy_light 0.20.1; `PointLight` gained: `contact_shadows_enabled`, `shadow_maps_enabled` (used in 1 files)
+```
+
+Sections are ranked by how many of your files they touch and cut to a token budget (`--max-tokens`, default 4000).
+
+## Does it help?
+
+I measured this on 12 Bevy 0.20 tasks with `claude-opus-5-5`. They covered observers, component hooks, picking, UI buttons, text, glTF scenes, lights, bloom and a few others. Every task has an official Bevy 0.20 example that compiles with the same feature set, so each one is solvable. A run passes when `cargo check` succeeds and the code contains what the task asked for. The two conditions differ only in the system prompt. Control gets one line saying the project pins Bevy 0.20.1. The notes condition gets that line plus a 4,000-token notes file, frozen before the first run.
+
+Writing `main.rs` in one reply, with no tools and 5 samples per task:
+
+| | control | with notes |
+|---|---|---|
+| compiles | 31/60 (52%) | 55/60 (92%) |
+| mean compiler errors | 2.4 | 0.1 |
+| deprecation warnings | 25 | 0 |
+| cost per call | $0.036 | $0.090 |
+
+As an agent that can run `cargo check` and fix its own errors, with 3 samples per task:
+
+| | control | with notes |
+|---|---|---|
+| compiles | 36/36 | 36/36 |
+| median turns | 6 | 3 |
+| median wall time | 38s | 25s |
+| cost per session | $0.112 | $0.139 |
+
+With a compiler in the loop Opus gets there either way, by reading the errors. The notes halve the turns. On tasks this small they also make each session about 24% more expensive, because the notes ride along in every prompt. Wall times are rough, since two sessions shared the CPU.
+
+The one task the notes didn't fix was loading a glTF scene (0/5 in both conditions). The migration guide renames `SceneRoot` to `WorldAssetRoot` in a list that the excerpt cut off. The current version always keeps guide lines that name an item your code uses. I haven't rerun the benchmark since that fix, because tuning on the test set would inflate the number.
+
+I also checked the API diff itself against the compiler. I took Bevy 0.18 examples, compiled them against 0.20.1, and asked whether the diff had flagged what broke. On 20 examples held out from all tuning, it flagged all 8 that broke. 19 of their 25 compiler errors (76%) name an item the diff flagged. Only 16 of the 42 items it predicted would break showed up in an error. That 38% is a lower bound, since rustc stops reporting some errors once others appear.
+
+Everything to rerun this is in the repo. The tasks are in `bench/tasks.json`, the frozen notes in `bench/notes.md`, the runner in `scripts/bench.py`, and per-run results in `bench/results-*.json`.
+
+## How it works
+
+1. **Find what's new.** For every package in `Cargo.lock` that you depend on, or that extends a name you depend on (`bevy_ecs` for `bevy`), it asks crates.io for release dates. The newest release from before the cutoff is the version the model knows. A `0.0.x` upload made long before the real releases counts as a name reservation, so that crate is treated as new.
+2. **Diff the APIs.** It builds rustdoc JSON for both versions in a throwaway package and caches it in `~/.cache/stalecrate`. Then it walks the public items, including methods, fields and enum variants. An item that disappears from one crate and shows up in a crate that's new in this version counts as moved. Changes that only touch trait bounds or lifetime names get dropped, because they rarely break callers.
+3. **Find what you use.** It runs a text scan of your `.rs` files with comments stripped. A removed name that still exists in another crate (`render_graph::Node` vs `bevy_ui::Node`) only counts when you write the qualified path. This step is an estimate, not name resolution.
+4. **Explain it.** It looks for migration guides shipped inside the crate (Bevy ships `_release-content/migration-guides`), `MIGRATION.md`/`UPGRADING.md`, and changelog entries for the versions in range. If the crate ships none of those, it uses GitHub release notes, and `GITHUB_TOKEN` raises the rate limit. Each used item links to the section that names it. Anything left over gets a one-line note with the old and new signature.
+
+## Limits
+
+- Building rustdoc JSON needs a nightly toolchain, and the JSON format changes between nightlies. I tested with format version 61 (nightly 2026-10-06).
+- Building docs runs build scripts, so crates that need missing system libraries get skipped. On the test machine that meant `bevy_audio` and `bevy_dev_tools` (ALSA) and `bevy_gilrs` (udev).
+- The first `sync` on a dependency tree the size of Bevy took 12 minutes. Later runs use the cache.
+- Usage matching is textual, so a type you shadow with your own of the same name can still match.
+- The benchmark covers one model and one crate family. I haven't measured crates that ship no migration guide, such as egui or wgpu.
+
+## License
+
+MIT or Apache-2.0, at your option.