Does vscode-front-matter run?

Argusic could not verify that vscode-front-matter runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.

How did Argusic test vscode-front-matter?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9d74f1c66154. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test vscode-front-matter?

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 vscode-front-matter take to install?

0.9 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 vscode-front-matter need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing vscode-front-matter?

2 things broke in the recorded run. Each one, and the time it cost, is listed on this page.

Where is the evidence for vscode-front-matter?

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.

vscode-front-matter

Front Matter is a CMS running straight in Visual Studio Code. Can be used with static site generators like Hugo, Jekyll, Hexo, NextJs, Gatsby, and many more...

Could not verifysource: GitHub homepageTypeScriptMITcommit 9d74f1c66154

TypeScript, MIT licensed. The project labels itself: cms, content management, content management system, hacktoberfest, markdown, static site, static site generator and vscode.

Argusic could not get vscode-front-matter running. An Argusic agent installed it in 0.9 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.

npm install succeeded, all 3 webpack bundles build successfully (extension.js 1217 KB, dashboard.main.js 8.5 MB, panel.main.js 10 MB), npm pack creates valid 1.2 MB .tgz (713 files), tsc reports 0 errors in src/, but the VS Code extension cannot be launched without the VS Code runtime which is not available in this container
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 30 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 30 / 100
cost of the verifying run: $0.05 (measured)
recorded runs: 2
last tested: 2026-10-03
stars: 2,543
forks: 108
open issues: 97
watchers: 11
size: 43 MB
created: 2019-08-23
last push: 2026-09-20

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-03. 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.

No test framework or test files exist in the repository
VS Code runtime not available in container; extension cannot be launched interactively

Install time: under a minute
Cold machine to finish: 8 minutes
Errors hit and fixed: 2 hit, 0 fixed with no human help
How the result was proved: npm run build:ext exited 0 with 3 successful compilations (extension, dashboard, panel); npm test-compile (tsc) reports 0 src/ errors; npm pack created valid 1.2 MB .tgz package with 713 files; npm pack unpacked size 3.2 MB; extension.js parses as valid JavaScript via node
Model tokens used: 73,938
Exact commit tested: 9d74f1c66154
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
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

    ],
    'test_depth': 'tier3_none',
    'notes': 'npm install added 1383 packages. npm run build:ext compiled all 3 webpack bundles (ex…
    'verified_how': 'npm run build:ext exited 0 with 3 successful compilations (extension, dashboar…
    'final_state': 'npm install succeeded, all 3 webpack bundles build successfully (extension.js 1…
}
print(json.dumps(report))
\"" in /work/repo
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": false, "install_minutes": 0.9, "errors": [{"msg": "…
tokens used
73,938

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

Installed in 0.9 minutes, faster than the median of the 10 comparable projects Argusic has measured.
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

An agent with no time limit did not get it running.
Hit 2 errors during setup, 2 of which were not solved.

Of the 11 cms projects Argusic has installed and timed, vscode-front-matter was the 2nd fastest to reach a running state, and 9 of 11 reached one at all.

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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Did not run	30.00	0.05	2026-10-03 04:29 UTC
Argusic Runner	1/3	Did not run	30.00	0.03	2026-10-03 04:20 UTC

Topics (from GitHub)

cms content-management content-management-system hacktoberfest markdown static-site static-site-generator vscode vscode-extension

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/vscode-front-matter.svg)](https://argusic.com/subject/vscode-front-matter)

Questions

Does vscode-front-matter run?: Argusic could not verify that vscode-front-matter runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test vscode-front-matter?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9d74f1c66154. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test vscode-front-matter?: 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 vscode-front-matter take to install?: 0.9 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 vscode-front-matter need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing vscode-front-matter?: 2 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
How does vscode-front-matter compare with the alternatives?: Of the 11 cms projects Argusic has installed and timed, vscode-front-matter was the 2nd fastest to reach a running state, and 9 of 11 reached one at all.
Where is the evidence for vscode-front-matter?: 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.