Every version we've recorded.
Including the blanks.
Most FiveM stores publish no version and no last-update date at all, so a buyer cannot tell a resource maintained last week from one abandoned in 2023. This page is the opposite habit, kept from the day before launch: every version number we hold, the date attached to it, and the products that have no entry yet.
Read it for what it is. These are versions recorded pre-release — nothing on this page has shipped, there is no public download of any of it, and the runtime state is the same as everywhere else on this site: no runtime proof published — pending Shadow bench. The entries carry a version and a date because that is what the catalog holds; they carry no release notes, because it does not. We would rather publish the blank than fill it.
Versions recorded
6 / 6
listed products carry a version and a date in the catalog. The other 0 carry none and are listed below as pending rather than left off the page.
Released
0
products. A recorded version is a build the studio cut, not a product you can download. Publishing is gated portfolio-wide, so every entry below is a pre-release record.
Runtime proof
Pending Shadow bench
No version below has a published capture of its core loop completing in a live FiveM world: no runtime proof published — pending Shadow bench. See the Proof Center for the full gap list.
Recorded versions
01 / 046 versions on file, newest first.
One block per product, grouped under the date its version was recorded. Version and date come straight from the catalog entry the product page reads — there is no second copy of them to drift.
2026-09-10
Heatline (vf_drugs)
- Not released. v1.1.0 is a build the studio cut; there is no public download of it.
- Escrowed core, open config and bridge — exact manifest at release.
- Tested framework versions publish with the release QA matrix.
- resmon [measured-pending] · no runtime proof published — pending Shadow bench.
No itemised change notes exist for this version. The catalog records a version and a date; it does not record notes, and we do not write them after the fact.
2026-09-02
ForgeCore (vf_core)
- Not released. v1.5.0 is a build the studio cut; there is no public download of it.
- 100% unescrowed — read everything before you run it.
- Tested framework versions publish with the release QA matrix.
- resmon [measured-pending] · no runtime proof published — pending Shadow bench.
No itemised change notes exist for this version. The catalog records a version and a date; it does not record notes, and we do not write them after the fact.
TitleLock Garage (vf_garage)
- Not released. v1.0.3 is a build the studio cut; there is no public download of it.
- Escrowed core, open config and bridge — exact manifest at release.
- Tested framework versions publish with the release QA matrix.
- resmon [measured-pending] · no runtime proof published — pending Shadow bench.
No itemised change notes exist for this version. The catalog records a version and a date; it does not record notes, and we do not write them after the fact.
2026-07-09
CityPulse (vf_announce)
- Not released. v1.1.0 is a build the studio cut; there is no public download of it.
- 100% unescrowed — read everything before you run it.
- Tested framework versions publish with the release QA matrix.
- resmon [measured-pending] · no runtime proof published — pending Shadow bench.
No itemised change notes exist for this version. The catalog records a version and a date; it does not record notes, and we do not write them after the fact.
2026-07-05
MoneyTrail (vf_banking)
- Not released. v1.0.0 is a build the studio cut; there is no public download of it.
- Escrowed core, open config and bridge — exact manifest at release.
- Tested framework versions publish with the release QA matrix.
- resmon [measured-pending] · no runtime proof published — pending Shadow bench.
No itemised change notes exist for this version. The catalog records a version and a date; it does not record notes, and we do not write them after the fact.
2026-07-04
ShiftWorks (vf_jobs)
- Not released. v1.0.0 is a build the studio cut; there is no public download of it.
- Escrowed core, open config and bridge — exact manifest at release.
- Tested framework versions publish with the release QA matrix.
- resmon [measured-pending] · no runtime proof published — pending Shadow bench.
No itemised change notes exist for this version. The catalog records a version and a date; it does not record notes, and we do not write them after the fact.
Awaiting a first entry
02 / 040 listed products have no recorded version.
These are on the page precisely because they have nothing to show. A store that lists only the products with a version tells you it has a changelog; a store that lists the blanks tells you what the changelog is worth.
Dated integrity results
03 / 042 measured results, with method and date.
Separate from the version ledger on purpose: these are engineering test results the studio filed with a date, a method, and an evidence path, reproduced here word for word. They are not runtime proof of the product in a live world: no runtime proof published — pending Shadow bench. They are the only rows on this page carrying the measured mark.
MoneyTrail (vf_banking)
kill-mid-transfer ×10 → reconcile drift = 0
Method: crash-recovery cycles with full ledger reconciliation
Evidence: Vice_Forge/products/vf-banking (reconcile evidence, R19)
MoneyTrail (vf_banking)
20 concurrent transfers → 1 success, 0 duplicates
Method: concurrency race test; 584-row audit ledger verified symmetric on Qbox + standalone
Evidence: Vice_Forge/products/vf-banking (studio test evidence)
The entry contract
04 / 04What every entry will carry from the first release.
A commitment, not a description of something that exists. None of it is in force yet, because nothing has shipped — it is written down now so it can be held against us later.
- 01
A semantic version
Major, minor, patch — with the rule stated: a breaking change takes the major, and we do not renumber to look busier.
- 02
The date it was cut
The date on the entry is the date the build was cut, not the date the page was edited. That is the only reading that makes a changelog worth checking.
- 03
What changed, itemised
Added, changed, fixed, removed — per item, in the words of the change. Nothing is summarised into 'improvements and bug fixes'.
- 04
Breaking changes, flagged first
Anything that requires a config edit, a SQL migration, or a start-order change is called out at the top of the entry, with the migration step written out.
- 05
Security advisories, separately
Security fixes get their own dated notice rather than being buried in a patch line. No advisory has ever been issued, because nothing has shipped.
- 06
The measurement, when one exists
A resmon reading enters an entry only with its artifact version, framework, method, and date attached. Until then the field reads [measured-pending].
Every version, date, and count on this page is derived from the same catalog entry the product pages read, so the two can never disagree. Nothing here is released, nothing here is purchasable, and nothing here is benched: no runtime proof published — pending Shadow bench. When a build ships, this page gains a dated entry with its notes — it does not gain a number that quietly changed.