brisa

The Web Platform Framework.

Runssource: GitHubhomepageTypeScriptMITcommit 555b635d281c

TypeScript, MIT licensed. The project labels itself: hacktoberfest, javascript, jsx, server components, server rendering, signals, static site generator and streaming.

brisa runs. An Argusic agent installed it in 33 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Brisa framework v0.2.15 builds and runs on bun 1.3.0: CLI produces usage output, core module bundles (out/core, server, client, macros, cli) verified, 1331 of ~3000+ total tests pass, adapter-vercel and brisa-pandacss packages work, i18n/SSR/routing/prerender/actions/RPC subsystems functional.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
2
last tested
stars
780
forks
29
open issues
55
watchers
17
size
17 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing brisa, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • 5-9 test files hang due to Bun.build() inside macro deadlock on bun 1.3.0 (process-i18n, pre-entrypoint-analysis, generate-entrypoint-code, get-client-build-details, client-build integration). CONTRIBUTING.md confirms ~9/3000 tests have Bun version issues.10 minutes
  • 8 test failures (1331 pass, 13 todo, 8 fail across 85 files)5 minutes
  • Bun 1.4.5 build failed: Bun.build() cannot be called inside macros, causing deadlock3 minutes
  • create-brisa tests failed: rm -rf permission denied and Bun.$ with rm not allowed
Install time
33 minutes
Cold machine to finish
34 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
bun packages/brisa/index.js --help returned usage text; bun test ran 1331 passed, 13 todo, 8 failed across 85 files; adapter-vercel, brisa-pandacss, CLI, AST, transpile, signals, i18n, SSR, RPC, prerender modules all verified
Model tokens used
314,368
Exact commit tested
555b635d281c
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

 succeeded in 0ms:
167
Now I have all the data I need. Note the timing: let me verify the elapsed time from the first npm …
exec
/bin/sh -lc 'date +%s' in /work/repo
 succeeded in 0ms:
1795366243
Now I have all the data needed for the final report. Let me produce the output.
2026-11-22T16:51:03.643060Z ERROR codex_core::session: failed to record rollout items: thread 01a20…
tokens used
314,368
Now I have all the data needed for the final report. Let me produce the output.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 33 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.

Of the 12 hacktoberfest projects Argusic has installed and timed, brisa was the 12th fastest to reach a running state, and 11 of 12 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.09
Argusic Runner1/3Runs100.000.64

Topics (from GitHub)

hacktoberfestjavascriptjsxserver-componentsserver-renderingsignalsstatic-site-generatorstreamingtypescriptweb-components

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/brisa.svg)](https://argusic.com/subject/brisa)

Questions

Does brisa run?
Yes. brisa runs. Argusic installed and launched it on a clean machine in 33 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test brisa?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 555b635d281c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test brisa?
The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does brisa take to install?
33 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does brisa need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing brisa?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does brisa compare with the alternatives?
Of the 12 hacktoberfest projects Argusic has installed and timed, brisa was the 12th fastest to reach a running state, and 11 of 12 reached one at all.
Where is the evidence for brisa?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion