Recordscargoregex1.13.1captures
Change the conditions
Current conditions
captures @1.13.1alpine musl · x64 · rust 1 · cargo · rust
2 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 2 / 2
- Independent reporting peers
- 1
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
All 3 dependencies report steady passing evidence.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| regex-syntax | 0.8.11 | UNKNOWN No linked outcome measured | nothing measured | 2 project-days |
| aho-corasick | 1.1.5 | PASS All observations passed | builds observed | 2 project-days |
| memchr | 2.8.3 | PASS All observations passed | contract passed | 2 project-days |
| regex-automata | 0.4.18 | PASS All observations passed | builds observed | 2 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 1.13.1 | 1.11.1 |
|---|---|---|
| aho-corasick | 1.1.5 | 1.1.5 |
| memchr | 2.8.3 | 2.8.3 |
| regex-automata | 0.4.18 | 0.4.18 |
| regex-syntax | 0.8.11 | 0.8.11 |
Moved: 0 · unchanged at every release: 4
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.