• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

decentraland / asset-bundle-registry / 32895184916
73%
main: 73%

Build:
Build:
LAST BUILD BRANCH: 2.5.2
DEFAULT BRANCH: main
Ran 25 Aug 2026 08:28PM UTC
Jobs 1
Files 87
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

25 Aug 2026 08:17PM UTC coverage: 73.247%. Remained the same
32895184916

push

github

web-flow
fix(auth): upgrade @dcl/crypto-middleware to 6.3.0 to close the folded signer-key bypass (#134)

* fix(auth): upgrade @dcl/crypto-middleware to 6.3.0 to close the folded signer-key bypass

`rejectIfSigner('decentraland-kernel-scene')` read the exact `signer` key, so
metadata delivering `{"Signer":"decentraland-kernel-scene"}` presented no
`signer` at all and the predicate treated the field as absent — answering
"allowed" for a request that visibly names the signer the gate exists to refuse.
The scene request then reached the handler as an ordinary user-signed one.

This is reachable on the strict, current-format path. Re-spelling the key
changes the signed bytes, so the request has to be signed that way, which a
scene-driven client can simply do; the signature over the re-spelled metadata is
genuinely valid. It is not only a legacy-payload quirk.

6.3.0 adds a `hasFoldedVariant` guard to `canonicalField` and
`requireCanonicalField`: a key that case-folds to the declared field without
being spelled exactly that is now a rejection rather than an absence.

The caret range already admitted 6.3.0, so the lockfile refresh is the
load-bearing change here — the declared range is bumped alongside it only to
make the intent explicit.

The added regression test signs the re-spelled metadata with the current 6.x
payload so it exercises the strict path. Pinned back to 6.2.0 it fails with a
200: the scene request goes all the way through.

* test: reuse the shared signed-fetch helpers from @dcl/test-helpers

The local getIdentity/getAuthHeaders in test/utils.ts were a hand-rolled copy
of the ADR-44 signing that @dcl/test-helpers already provides. Bump the package
to ^0.3.2 — the first release whose getAuthHeaders signs the unfolded 6.x
payload rather than the pre-6.0.0 folded one — and re-export its helpers so the
payload format lives in one place that stays in step with @dcl/crypto-middleware.

createRequestMaker now calls getSignedAuthHeaders instead of repeating... (continued)

670 of 957 branches covered (70.01%)

Branch coverage included in aggregate %.

1753 of 2351 relevant lines covered (74.56%)

40.79 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32895184916.1 25 Aug 2026 08:28PM UTC 174
73.85
GitHub Action Run
Source Files on build 32895184916
  • Tree
  • List 87
  • Changed 54
  • Source Changed 0
  • Coverage Changed 54
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #32895184916
  • d932a02e on github
  • Prev Build on main (#32530337550)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc