3 findingsStatic scanned
Wires agent-to-agent messaging into the Hermes agent and has it react to new mail while it works.
2.3k installs/moFSL-1.1-Apache-2.0
Ours Network Install
ours.network · Template
Installs the ours.network suite onto one machine and wires it into your agent tools. It sets up a single shared daemon that runs as a background service on Linux or macOS, adds the ours plugin to detected Claude Code, Codex and Hermes installations, and starts cowork and Telegram connectors over that daemon. When no Fleet file exists yet, it also writes a stopped Fleet starter with a coordinator, a health watchdog and a ten-minute health loop, leaving you to review and start it.
Written by ooruby from the README of @ours.network/install 1.1.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Puts the ours.network packages, shared daemon and agent plugins in place in one run, with a progress display and guided next steps.
What you could do with it
- Preview the whole install with a dry run that writes no files and starts no processes.
- Install the ours plugin into the Claude Code, Codex and Hermes installations it detects on your machine.
- Review the stopped Fleet starter it writes, then bring Fleet up when you are ready.
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
- Command execution is bounded
- inventory
- node child_process (lib/effects.mjs:14)
- synchronous shell execution (lib/effects.mjs:52)
- synchronous shell execution (lib/effects.mjs:74)
- synchronous shell execution (lib/effects.mjs:130)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
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
The all-in-one ours.network installer: one shared daemon, MCP, cowork, Telegram, Fleet, harness plugins, Human identity, stopped Fleet starter, progress UI, and guided next steps.
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 1.1.1, the file with digest sha512-jXbti+gWZ0bzMG8GbcIsL7ja2j3sto0V8La0G84LQBnnXtn7/lAxh+lyBTSMulaWQEbsWYDq8Jd2+2kLsh/FEg==, 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 @ours.network/install@1.1.1Pinned to 1.1.1, 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
- @ours.network/install
- Version read
- 1.1.1
- 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/ours-network-install)About this listing
- Kind
- Template
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
More from ours.network
See the storefrontSimilar templates
All templatesClean scanStatic scanned
Scaffolds OpenUI agent apps, mints Cloud API keys and turns component libraries into model prompts.
45.8k installs/moMIT
1 findingStatic scanned
Creates a new Mastra app with one command and helps you set up example agents and a model provider.
27.4k installs/moApache-2.0
1 findingStatic scanned
Scaffolds a new Tangle agent application with either a tool loop or a complete chat interface.
13.5k installs/moMIT
Verification 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.