The vmodal_sdk_flutter README pins a tag its own workflow never creates, and ships 1.3.0 as source only
V- Modal AI: Visual Video / Image Search - SDK Flutter
At a glance
- What is it?
- V-Modal's Flutter SDK does semantic video and image search with credentials the host app owns. Its documentation is unusually explicit about its own limits, to the point of admitting that the recommended production pin may not exist. Two versions are in play, one of them exists only as source, and the getting started section is a prompt you paste into a coding agent rather than a set of steps.
- Who is it for?
- This SDK is a reasonable choice for a Flutter app that needs to find moments inside its own video library by meaning rather than by metadata, and the security posture is better than most mobile SDKs of its kind: your key is never persisted by the library, no login screen is imposed on you, and a backend path exists so the app never receives a master key. Three things to settle before you build on it.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 43 days ago.
- What is it written in?
- Mainly Dart, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- v-modal/vmodal_sdk_flutter2,154 ★ · +722
| Repository | 2026-09-17 | 2026-11-15 |
|---|---|---|
| v-modal/vmodal_sdk_flutter | 1.4k | 2.2k |
722 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The recommended production pin is a tag the workflow never creates
The integration section gives two dependency snippets and then explains why one of them may not work. The first is the pub.dev package at an exact version, which it calls the preferred choice for production. The second points at a Git URL with a version tag in the ref field, and the instruction above it is to use that tag only after a pub.dev release has actually created it, because the default source-only public workflow does not create it. If such a release happened without a package publication, the instruction is to replace the ref with a full forty character commit hash from the public repository. So the snippet as printed is a template whose ref may not exist:
dependencies:
vmodal_sdk_flutter:
git:
url: https://github.com/v-modal/vmodal_sdk_flutter.git
ref: v1.2.3The page also says the default branch is fine for evaluation and development and is not a production pin, and the repository publishes no releases, so nothing in the repository itself lets you check which tags exist.
Two versions, one of them only ever source
Three paragraphs after the dependency snippets explain the version situation more precisely than anything else on the page. The opt-in user session API is described as part of the 1.3.0 source release, with a direct instruction to use that released public source revision for it, because the 1.2.3 package and tag shown earlier do not contain those additions. Then the second half: a source-only GitHub Actions export does not publish 1.3.0 to the package index and does not create a version tag. So the two documented versions reach users by different routes, the newer one only as source, and a developer following the production advice verbatim gets the older API without the session isolation code. That is a candid paragraph and it is the kind of thing most SDK documentation would leave out, but it means version selection here is a decision rather than a lookup.
Getting started is a prompt for a coding agent
One section is titled with a doubled word about getting started, and its instruction is to copy the following block into your coding agent. The block is not prose; it is an imperative script for a machine. Clone the repository, enter the directory, read the repository instructions and the full application example before changing anything, use the pinned Flutter toolchain rather than installing a global one, then run an install script and three build subcommands for dependencies, analysis and tests, then start an emulator or a simulator and list devices by asking the install script where the toolchain lives. The block ends mid-command, on an unclosed quote after a variable that would invoke the Flutter binary. It is an unusually literal document, aimed at an agent that can execute it, and it says more about how the maintainers expect people to use the SDK than a tutorial would.
Two example directories share the number 05
The example folder holds seven directories, and the numbering collides. There is a full application example, a users example, a closed circuit television example, one generically named example, then two directories that both start with 05, one for a hosted backend platform and one for a user login flow against it, then a sixth-numbered directory for backend authentication. Nothing in the README explains the collision or which of the two 05 directories is current, and the documentation links point at the full app example and at the sixth one specifically, so a reader following links lands correctly by accident rather than by numbering. There is also a readme inside the example folder itself, which means the authoritative index of these directories may not be the one on the front page.
The backend authentication path is documented as not deployed
The page describes two ways to authenticate, and the second one comes with an unusual warning. In the direct setup, the host app holds the runtime key. In the backend setup, the app connects through a call that takes the expected signed-in user identifier and the expected project identifier, and loads a short-lived token envelope from your own server, which uses a registered server credential to mint it. Then the caution: this source API requires corresponding registered origin, worker and upstream capabilities, and is not a claim of live deployment. The rest of that section is written carefully, saying the client receives no master key, constructs no collection selector and adds no identity headers, that the SDK confirms the binding and grants before returning and coalesces renewal, and that you should close the session at the start of a logout or account switch. What is missing is a deployment status, which is the one thing you would need to know before choosing it.
Letters, digits and underscore, capped after encoding
The naming rules for projects, collections and streams are the most precise paragraph in the documentation, and the reason is not obvious until the last sentence. Identifiers accept letters, digits and the underscore character only, are trimmed, and are limited to eighty characters. Project and collection names cannot contain the reserved double separator, and their encoded backend value is also limited to eighty characters, with the SDK performing the encoding internally. So the eighty character budget applies after encoding rather than before, which is why the permitted character set is so narrow and why the separator is reserved: both restrictions exist to make the encoded form predictable. Anything that generates identifiers from user input has to sanitise to that alphabet before it reaches the SDK, and a name containing a hyphen or a dot will be rejected rather than coerced.
A checksum manifest, a secret scanner, and six shell scripts
The repository root is mostly release machinery. There is a file whose name is a manifest of source checksums, a release metadata file, a release note, a secret scanning configuration for the repository history, a shell script whose name is a security check, and a publish ignore file alongside the ordinary package ignore file. Six shell scripts sit next to them, covering install, build, run, test and environment setup. The Flutter version is pinned in its own file rather than left to whatever the machine has, which is the same reason the getting started block refuses to let an agent install a global toolchain. A lock file is committed. Taken together this is a package that is trying to make its release verifiable and its toolchain reproducible, which is unusual in a mobile SDK and worth crediting before you spend an afternoon working out which version you can actually install.
Editorial conclusion
This SDK is a reasonable choice for a Flutter app that needs to find moments inside its own video library by meaning rather than by metadata, and the security posture is better than most mobile SDKs of its kind: your key is never persisted by the library, no login screen is imposed on you, and a backend path exists so the app never receives a master key. Three things to settle before you build on it. Which version you are actually pinning, because the two documented versions are distributed differently and only one of them is on the package index. Which authentication path you will use, because the backend-scoped one is documented as requiring server-side capabilities the page describes as not yet a claim of live deployment. And whether the identifiers your app generates will survive the naming rules, since only three kinds of character are allowed, an eighty character limit applied after encoding, and a reserved separator will reject some names that look perfectly reasonable to a developer.
Frequently asked questions
What is vmodal_sdk_flutter?
A Flutter SDK from V-Modal for visual video and image search. You upload video and then find moments by meaning, by spoken words, by text on screen or by imagery, with your app owning the interface and the credentials.
How do I add vmodal_sdk_flutter to a Flutter app?
Add it to your dependencies, using an exact published version from the package index for production or a pinned Git revision for a source build, then run `flutter pub get`. The main branch is described as suitable for evaluation only.
Does the V-Modal Flutter SDK store my API key?
No. The SDK never owns your login screen and never persists your key. You supply it at runtime through a provider, or your own backend mints short-lived scoped tokens against a registered server credential.
Which version of vmodal_sdk_flutter includes the user session API?
The 1.3.0 source release. The README states that the 1.2.3 package and tag do not contain those additions, and that a source-only export publishes neither a package release nor a version tag.
What are the naming rules for V-Modal projects and collections?
Identifiers accept letters, digits and one punctuation character only, are trimmed, and are limited to 80 characters. Project and collection names cannot contain the reserved double separator, and the encoded backend value is capped at 80 characters as well.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/v-modal-vmodal-sdk-flutter)Star history chart for your README
[](https://hysenlabs.com/projects/v-modal-vmodal-sdk-flutter)Was this useful?