Deployed bytecode matches signed release tag
Hyperlane's assessment for RD-F-136 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Hyperlane GitHub has no signed release-tag workflow identified. Data cache: changelog_present=false. No audits/ subdirectory in monorepo. Cannot verify signed-commit-to-deployed-bytecode match.
Sources #
- InternalData cache GitHub fields00-data-cache.json: github.changelog_present=falseretrieved 2026-05-17
- Hyperlane monorepohyperlane-monorepo: no /audits/ subdirectory in solidity/ per profile §11retrieved 2026-05-17
Methodology #
Determine whether the deployed runtime bytecode corresponds to a signed git tag in the protocol's repository.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol hyperlane factor RD-F-136 score gray collected_at 2026-05-16 23:03:56