inframap
Read your tfstate or HCL to generate a graph specific for each provider, showing only the resources that are most important/relevant.
Runssource: GitHubGoMITcommit f02f224cb0d0
Go, MIT licensed. The project labels itself: aws, diagram, flexibleengine, go, golang, graph, hcl and openstack.
inframap runs. An Argusic agent installed it in 1.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The Go project builds cleanly, all 8 test packages pass, and the binary prints correct version output, generates DOT graphs from both tfstate and HCL inputs, and prunes sensitive fields from state files.
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
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.
- Install time
- 2 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test ./... exited 0 with 8 packages passing; ./inframap version returned 'The current version is: f02f224'; ./inframap generate generate/testdata/aws_hcl_sg.tf and generate/testdata/azure.tfstate both produced valid DOT graph output on stdout; ./inframap prune azure.tfstate produced sanitized JSON
- Model tokens used
- 48,013
- Exact commit tested
- f02f224cb0d0
- 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.
tokens used 48,013 All tasks complete. Here's the summary: **Install**: Go 1.22.0 binary extracted to `/tmp/go` (no root/sudo available). `go mod download` fe… **Launch**: Binary executed immediately. Every subcommand verified: - `./inframap version` → `The current version is: f02f224` - `./inframap generate generate/testdata/aws_hcl_sg.tf` → valid DOT graph output describing AWS res… - `./inframap generate generate/testdata/azure.tfstate` → valid DOT graph output describing Azure r… - `./inframap prune generate/testdata/azure.tfstate` → sanitized JSON state with sensitive attribut… - `./inframap --help` → all subcommands listed **Tests**: `go test ./...` — **14 package directories checked, 8 with test files; all passed.** Zer… **Errors**: None. The repo is self-contained with no third-party API keys, no external services, an…
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.
- Installed in 1.5 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 aws projects Argusic has installed and timed, inframap was the 2nd fastest to reach a running state, and 4 of 4 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 1.5 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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
Topics (from GitHub)
awsdiagramflexibleenginegogolanggraphhclopenstackterraformtfstate
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/inframap)Questions
- Does inframap run?
- Yes. inframap runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test inframap?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f02f224cb0d0. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test inframap?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does inframap take to install?
- 1.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 inframap need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing inframap?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does inframap compare with the alternatives?
- Of the 4 aws projects Argusic has installed and timed, inframap was the 2nd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for inframap?
- 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.