knowledge-catalog
Google Cloud Knowledge Catalog Tools and Samples
Runssource: GitHubhomepageTypeScriptApache-2.0commit 22efaa540277
TypeScript, Apache-2.0 licensed.
knowledge-catalog runs. An Argusic agent installed it in 9.5 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
OKF Python reference agent installs and tests pass (39/39); visualize subcommand generates working HTML bundles; kcmd CLI builds and passes 38/40 tests (2 fail only due to missing gcloud); enrich subcommand, samples, and kcagent require GCP credentials not available in this environment.
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 80 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.
- npm install for toolbox/enrichment hangs indefinitely (depends on file:../mdcode and hits resolution deadlock)3 minutes
- 2 kcmd tests fail: missing gcloud CLI binary (expected for GCP-dependent components)0.5 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 2 hit, 0 fixed with no human help
- How the result was proved
- cd okf && .venv/bin/pytest -v: 39 passed; .venv/bin/python -m reference_agent visualize --bundle bundles/crypto_bitcoin wrote 9 concepts, 21 edges, 51171 bytes; cd toolbox/mdcode && npm run test: 38 pass 2 fail; ./dist/kcmd --help prints usage for 6 subcommands; ./dist/kcmd --version prints kcmd/1.0.0
- Model tokens used
- 451,176
- Exact commit tested
- 22efaa540277
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
1. **OKF (Python reference_agent)**: `pip install -e .[dev]` succeeded. All 39 tests passed. The `v… 2. **Toolbox/mdcode (kcmd)**: `npm install --no-package-lock` succeeded (lockfile had private regis… 3. **Toolbox/enrichment (kcagent)**: npm install hangs indefinitely (depends on `file:../mdcode`). … 4. **Samples**: Both sample directories require GCP credentials and depend on google-adk. tokens used 451,176 Now I have a clear picture. Let me compile the final ARGUSIC_RESULT. **What was observed:** 1. **OKF (Python reference_agent)**: `pip install -e .[dev]` succeeded. All 39 tests passed. The `v… 2. **Toolbox/mdcode (kcmd)**: `npm install --no-package-lock` succeeded (lockfile had private regis… 3. **Toolbox/enrichment (kcagent)**: npm install hangs indefinitely (depends on `file:../mdcode`). … 4. **Samples**: Both sample directories require GCP credentials and depend on google-adk.
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.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Took 9.5 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
- Hit 2 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 13 TypeScript projects Argusic has installed and timed, knowledge-catalog was the 10th fastest to reach a running state, and 11 of 13 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.
- A quick evaluation: it was running 9.5 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/knowledge-catalog)Questions
- Does knowledge-catalog run?
- Yes. knowledge-catalog runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test knowledge-catalog?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 22efaa540277. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test knowledge-catalog?
- 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 knowledge-catalog take to install?
- 9.5 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 knowledge-catalog need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing knowledge-catalog?
- 2 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
- How does knowledge-catalog compare with the alternatives?
- Of the 13 TypeScript projects Argusic has installed and timed, knowledge-catalog was the 10th fastest to reach a running state, and 11 of 13 reached one at all.
- Where is the evidence for knowledge-catalog?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.