Clean scanStatic scanned
The fastest way to start training your own Language Model. Create production-ready LLM training projects in seconds.
5.4k installs/moMIT
Theanikrtgiri Create Llm
theanikrtgiri · Template
The fastest way to start training your own Language Model. Create production-ready LLM training projects in seconds.
Not claimed by its maker. Is this yours? Prove it and answer the findings
What else was checked
Publisher and name
- Name matches another package once punctuation is ignoredIndistinguishable from create-llm to anyone typing quickly.
Maintenance
At riskLast release 29 Oct 2025 (2.2.3), 336 days before this check on 1 Oct 2026.
Read from the npm registry's publish history, read by the nightly publisher check.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Tool description integrity
- nothing to read
- Pattern set 1.0 matched nothing on 2026-10-04, but none of the descriptions the package ships runs to 120 characters, so there was little for a rule to read.
- It reads the descriptions the package ships, not what the server says when it runs, and a clean description is not the same thing as a safe tool.
- Row-level security
- nothing to read
- No Supabase migrations in the 30 files of the published package read on 2026-10-02, so there was nothing for this check to read.
- Not covered: A reading of files cannot prove a policy is enforced at run time: whether these migrations were applied, whether row-level security was switched on another way (the dashboard, SQL run by hand), or what a table holds. A database only the app's own server can reach (SQLite, or Postgres behind a server that holds the only connection) needs no row-level security for this reason, and its migrations are not read.
- Object-level authorisation
- nothing to read
- No Supabase migrations in the 30 files of the published package read on 2026-10-02, so there was nothing for this check to read.
- Not covered: Whether the app means every account to edit everything (an admin tool whose only account is its owner's), whether sign-up is open (a dashboard setting), and anything about a policy whose expression looks at the row. Whether the migrations were applied is not known. Policies that let anyone read every row are not counted here.
- CORS configuration
- no match, 24 code files read
- App check set 1.0 matched nothing across 24 code files, 30 files of the published package read on 2026-10-02.
- Not covered: Whether it matters. A server that checks a token sent in a header gives a foreign page nothing it could not do without the browser, and a server bound to the loopback address is reachable only from pages open on the same machine (which is still every page that machine opens). A value chosen at run time, such as a variable that falls back to *, is not read: the hand count found one such server, and it is not in the figure.
- Not covered: Whether the server reads cookies at all, whether the echo is guarded by a check this reading does not follow, and anything decided at run time.
- No shipped credentials
- no match, 30 files read
- App check set 1.0 matched no credential in a format it recognises, bundles included, across the 30 files of the published package read on 2026-10-02.
- Not covered: Whether a key still works (none is ever tried, because trying one would be using it), credentials in formats the check does not name, anything in a repository's history, and files the nightly reading does not reach when a package is over its caps.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Tool descriptions are read with pattern set v1.0, published with every rule, its sources and how often it has been wrong.
App checks are read with app check set v1.0, published with every rule, what it does not cover and how often it has been wrong.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
What it does
The fastest way to start training your own Language Model. Create production-ready LLM training projects in seconds.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The Assay Index sets out exactly what was read.
- Exactly what was read
- Version 2.2.3, the file with digest sha512-c54xSliN6AGc4pewQHB8GXcIROjP98ZwPNRsVz/4yupCKBRiX91+J5Wf3XOxjpEAlhLnbnZV6jQc6+hOvRPc3w==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y @theanikrtgiri/create-llm@2.2.3Pinned to 2.2.3, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
550 installs last month (via ecosyste.ms) · no published advisories · version current · checked 2026-10-03
Where this came from
- Registry
- npm
- Package
- @theanikrtgiri/create-llm
- Version read
- 2.2.3
- Resolved
- 2026-08-23
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/theanikrtgiri-create-llm)About this listing
- Kind
- Template
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-08-19
More from theanikrtgiri
See the storefrontSimilar templates
All templatesClean scanStatic scanned
CLI for OpenUI — scaffold generative UI chat apps and generate LLM system prompts from component libraries
45.8k installs/moMIT
1 findingStatic scanned
1 findingStatic scanned
Create a tested Tangle agent application with either a tool loop or a complete chat interface.
13.5k installs/moMIT
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.