- What does think.studio/nova-text-card actually do?
- It is a Laravel Nova card component that renders static text content on a Nova dashboard or resource screen. You can use it to add headings, notes, or instructional copy to admin pages. Functionally it is a thin wrapper around a PHP Card subclass, a Vue component, and a service provider registration. It carries no persistence, queue work, or domain logic.
- How do I install think.studio/nova-text-card in a Laravel Nova app?
- The usual pattern for a Nova card is composer require think.studio/nova-text-card followed by registering the card in your NovaServiceProvider's cards() or dashboard method. Because the package has no detected license and no maintainer signal, a straight Packagist install is not recommended. If you decide to use it, copy the source into nova-components/text-card in your own repository instead. That keeps the artifact first-party and removes it from composer audit and supply-chain noise.
- Is think.studio/nova-text-card compatible with Nova 4 and Nova 5?
- That is unverified. Nova 3 uses Vue 2 with Laravel Mix, while Nova 4 and 5 use Vue 3 with Vite, and those are incompatible at the component layer. Card packages often declare laravel/nova: * or omit the constraint entirely, so Composer can resolve a build that fails at runtime rather than at install time. Check the declared Nova major and the asset build config before assuming compatibility.
- Is there a built-in Laravel Nova alternative to this text card?
- Yes. Nova ships a native Laravel\Nova\Cards\Help card that renders arbitrary HTML, which covers most static text and instructional copy requirements. If your only need is displaying text on a dashboard, the Help card satisfies it with zero third-party dependency. Prototype with Help first before adopting any external card package. A bespoke text card is only around 60 to 120 lines if you need something custom.
- What license does think.studio/nova-text-card use?
- GitHub reports the license as NOASSERTION, meaning no recognized license file was detected. Absent an explicit grant, default copyright applies, so you have no clear right to use, modify, or redistribute the code. This is a legal blocker rather than a code review item. Do not merge it into a production application until you obtain a written license grant, ideally MIT.
- Does think.studio/nova-text-card support HTML content, and is it sanitized?
- The package displays custom text content, but whether it accepts raw user-supplied HTML and whether that HTML is sanitized is not documented. Unsanitized HTML inside an authenticated admin card is a stored-XSS path. If the card renders arbitrary HTML, review the Vue component and confirm sanitization before use. If content is hardcoded by developers only, the risk profile is much lower.
- Is think.studio/nova-text-card safe to run in production?
- Not as-is. A zero-star, zero-dependent package from an unverified author that runs inside an authenticated admin surface is a supply-chain risk. Review every file, especially the service provider and any asset build config, for outbound calls, obfuscation, or autoloaded side effects. The license gap and lack of maintenance also make it unsuitable for production without a legal gate and a full source review.
- Is think.studio/nova-text-card still maintained?
- There is no maintainer signal: zero stars, zero dependents, no meaningful description, and no release cadence to speak of. Treat it as abandoned and assume there will be no upstream bug fixes or security response. If you adopt it, vendor the code so you own future patches and upgrades yourself.
- How do I register the text card in a Nova dashboard or resource?
- Nova cards are registered through the cards() method on your dashboard class or resource, typically returning a new instance of the card class with any options passed to its constructor. Nova cards are an officially supported extension point, so the integration pattern itself is idiomatic. The exact constructor signature and options for this package are not documented, so read the Card.php source before wiring it up. If the assets are not committed, you may also need to build them with Node during deployment.
- Should I install think.studio/nova-text-card from Packagist or vendor the source?
- Vendor the source if you use it at all. Copying it into nova-components/text-card inside your own repository converts an unmaintained transitive dependency into first-party code you control and test. That also removes it from composer audit output and supply-chain exposure. Pin the exact Nova major, PHP version, and Node build versions the card was authored against, and lock the asset build into CI for reproducible deploys.