Clean scanStatic scanned
Hasna Logs
hasna · Agent
Hasna Logs aggregates logs and gives AI agents ways to read them. A command line lists, tails, summarises and pushes logs, scans pages with a headless browser and diagnoses problems. Its MCP server covers log search, raw event search, watch and export, test-report search, storage sync, page scans, issues and performance. The REST service runs on PostgreSQL, or as an on-box SQLite collector when you opt in, and its API stays locked unless a token is set.
Written by ooruby from the README of @hasna/logs 0.5.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Logs, test reports and page scan results sit in one service that your agent can search directly.
What you could do with it
- Tail the latest logs from the command line and ask for a summary of what happened.
- Search raw events and export them through the MCP server while your agent debugs a failure.
- Run a shared HTTP MCP server on localhost so several agents can read the same logs.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Log aggregation + browser script + headless page scanner + performance monitoring for AI agents
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.5.0, the file with digest sha512-TuRS8WBl8BOmXkg3pOoTKhDfWOPntvH8NDAcR+ErCctMLmIIRtYkTpzv8W20Nv6JXHnZA1uRUQ6tpx/WReHXVQ==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y -p @hasna/logs@0.5.0 logsPinned to 0.5.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @hasna/logs
- Version read
- 0.5.0
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/hasna-logs)About this listing
- Kind
- Agent
- Category
- Infrastructure
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
More from hasna
See the storefrontSimilar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.