notion-sdk-js
Official Notion JavaScript Client
Runs with mockssource: GitHubhomepageTypeScriptMITcommit 51268112018f
TypeScript, MIT licensed. The project labels itself: api, api client, javascript, js, notion and typescript.
notion-sdk-js runs, with stand-ins for the services it depends on. An Argusic agent installed it in 16 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
SDK installed, built, and all 5 main test suites pass (135 tests). SDK exports work with a mock Notion API server: users.list and users.retrieve return correctly formatted responses. Webhook signature helpers verify correctly.
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 56 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Compatibility test (compatibility.test.ts) hangs due to TypeScript compiler API resource constraints in the container
- Install time
- 16 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 5 suites 135 tests passed; node mock-server exercise returned users.list 1 result and users.retrieve user object; webhook sign/verify helpers validated correctly
- Model tokens used
- 154,060
- Exact commit tested
- 51268112018f
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2026-09-29T13:57:15.236516Z ERROR codex_core::session: failed to record rollout items: thread 01a0e…
2026-09-29T13:57:15.237305Z ERROR codex_core::session: failed to record rollout items: thread 01a0e…
tokens used
154,060
All findings are in. Let me compile the final report.
**Install & Build**: `npm ci` ran successfully (it auto-triggered `tsc` build via the `prepare` scr…
**Test suite**: 5 test suites — 135 tests — all passed with exit code 0. The `compatibility.test.ts…
**End-to-end verification**:
- SDK exports all documented symbols (`Client`, `APIErrorCode`, `isNotionClientError`, `LogLevel`, …
- Mock server test: `client.users.list({})` returned 1 result (`Test User abc-123`), `client.users.…
- Webhook helpers: `signWebhookPayload` generated a valid HMAC-SHA256 signature; `verifyWebhookSign…
**No unrecoverable errors encountered.**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
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- 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
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 16 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.
Of the 7 api projects Argusic has installed and timed, notion-sdk-js was the 5th fastest to reach a running state, and 4 of 7 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.05 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.02 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/notion-sdk-js)Questions
- Does notion-sdk-js run?
- notion-sdk-js runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 16 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test notion-sdk-js?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 51268112018f. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test notion-sdk-js?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does notion-sdk-js take to install?
- 16 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 notion-sdk-js need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing notion-sdk-js?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does notion-sdk-js compare with the alternatives?
- Of the 7 api projects Argusic has installed and timed, notion-sdk-js was the 5th fastest to reach a running state, and 4 of 7 reached one at all.
- Where is the evidence for notion-sdk-js?
- 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.