Weave Code
Json Laravel Package
armincms/json
A Laravel package that simplifies working with JSON data in Eloquent models. Fluent helpers let you read, write, query, and cast JSON columns, making nested structures and dynamic attributes easier to manage throughout your application.
A Laravel Nova field.
Frequently asked questions about Json
- What does the armincms/json package do?
- It is a Laravel Nova field that renders a JSON editor bound to an Eloquent attribute, so an admin can read and write JSON stored in a database column. It also ships a thin set of Eloquent casting helpers for accessing nested keys fluently. There is no domain logic, background processing, or end-user request-path footprint; it is an admin-surface tool only.
- Is armincms/json compatible with Nova 4, Nova 5, Laravel 10, or Laravel 11?
- Almost certainly not out of the box. The last release was 2020-06-18, which places it in the Nova 2/3, Laravel 6/7, PHP 7.x era. Nova 4 moved the field layer to Vue 3 and later majors tightened constraints further, so Composer will likely block resolution. Run composer why-not armincms/json on your estate first, and note that forcing constraints can still fail at render time because the Vue component contract changed.
- How do I install armincms/json?
- The mechanical install is a one-line Composer require followed by a field declaration in the relevant Nova resource. The real friction is version drift: on a modern Laravel and Nova stack the dependency graph usually refuses to resolve. Treat installation as a compatibility investigation, not a copy-paste step, and prototype in a scratch resource before touching a real table.
- Does armincms/json validate or normalize JSON before saving?
- There is no documented evidence of schema validation or normalization; the field appears to write the editor string through to the attribute. That permits silently malformed or semantically wrong JSON to persist and break every downstream reader of that column. This is the highest-severity risk class because it is quiet, data-level, and expensive to unwind after the fact.
- How does armincms/json interact with Eloquent JSON casts like array, json, or AsArrayObject?
- This is the subtle hazard in the write path. Nova fields typically set the attribute directly, so an array cast may double-encode the payload while a json cast may mask a malformed value instead of rejecting it. Verify the round trip in a scratch resource against your actual column type, and confirm whether you are on MySQL JSON or a plain TEXT column, before trusting it with production data.
- Is armincms/json still maintained?
- No. It has a single maintainer, no release in over four years, no changelog, and no security disclosure channel. With roughly 25 stars and zero dependents, there is no public evidence of anyone running it against current Nova. Assume zero upstream fixes for the life of the dependency and plan accordingly.
- What are the alternatives to armincms/json?
- If the requirement is a known schema of a dozen keys, Nova's built-in KeyValue field or a bespoke field wins on maintainability, validation, and permissions at comparable effort. If you genuinely need arbitrary JSON, the better route is to vendor or fork the small MIT-licensed field code rather than take a direct dependency. Both reframe the decision from adopting an abandoned package to owning a small piece of code.
- Can I fork or vendor armincms/json into my own codebase?
- Yes. The MIT license permits forking, internal redistribution, and closed modification, which is the escape hatch that makes the risk manageable. Fork into an internal namespace via a VCS repository entry, preserve the MIT attribution, and pin the version. Alternatively, inline the field class into app/Nova/Fields/ — it is likely a single class and cheaper to own at that size.
- Does armincms/json have a test suite or support modern PHP versions?
- There is no indication of a maintained test suite or coverage of PHP 8.1 through 8.3. Deprecations in that range, plus Laravel's evolving JSON casting options, are unpatched and will surface as upgrade-time blockers rather than steady-state noise. If you adopt it, plan to write your own tests and run them against your PHP and CI matrix.
- Is armincms/json safe to use for admin-authored JSON in production?
- Admin-authored JSON that is re-rendered unescaped is a stored-XSS vector, so the field and every downstream consumer of that column need review. Permission and audit requirements are also a concern, because a raw editor structurally cannot enforce schema or record granular change history. The gating decisions are which Nova majors you run today and at twelve months out, whether the need is truly arbitrary JSON, and whether you have a named owner with Vue and Nova front-end skill.
Weaver
How can I help you explore Laravel packages today?