modelos-secure 0.3.0 → 0.3.1

package/{dist/cli.js → cli.js}

@@ -23,7 +23,7 @@ if (existsSync(resolve(here, "wasm"))) {
 }
 // package.json
 var name = "modelos-secure";
-var version$1 = "0.3.0";
+var version$1 = "0.3.1";
 var type = "module";
 var bin = { "modelos-secure": "dist/cli.js" };
 var exports$1 = { "./hook": "./dist/hook/hook.mjs" };
@@ -46,7 +46,7 @@ var repository = {
 var package_default = {
 	name,
 	version: version$1,
-	"private": false,
+	"private": true,
 	type,
 	bin,
 	exports: exports$1,

package/package.json

@@ -1,36 +1,20 @@
 {
   "name": "modelos-secure",
-  "version": "0.3.0",
-  "private": false,
+  "version": "0.3.1",
+  "description": "Tests AI systems for Security, Safety and Quality. One command connects a system from its code.",
+  "license": "UNLICENSED",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/mn-chetan/modelos-secure.git"
+  },
   "type": "module",
   "bin": {
-    "modelos-secure": "dist/cli.js"
+    "modelos-secure": "cli.js"
   },
   "exports": {
-    "./hook": "./dist/hook/hook.mjs"
+    "./hook": "./hook/hook.mjs"
   },
   "engines": {
     "node": ">=22"
-  },
-  "files": [
-    "dist"
-  ],
-  "scripts": {
-    "build": "vite build"
-  },
-  "dependencies": {
-    "@modelos-secure/core": "workspace:*",
-    "@modelos-secure/scan": "workspace:*",
-    "@modelos-secure/schema": "workspace:*",
-    "yaml": "2.9.1"
-  },
-  "devDependencies": {
-    "vite": "8.3.6"
-  },
-  "description": "Tests AI systems for Security, Safety and Quality. One command connects a system from its code.",
-  "license": "UNLICENSED",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/mn-chetan/modelos-secure.git"
   }
-}
+}

package/dist/README.md

@@ -1,60 +0,0 @@
-# modelos-secure
-
-Tests an AI system for Security, Safety and Quality. One command in the system's repository connects it, with no code changes:
-
-```bash
-npx modelos-secure scan .
-```
-
-It reads the code the way an engineer would, starting where the app starts, draws the system's map and asks only what it cannot work out. Everything it decides goes into `modelos-secure.yaml`.
-
-Before it sends anything it asks once whether a model may read the code it needs, or only an outline of it, or nothing. Every answer it sends passes a filter that takes secrets out, and settings files, keys and credentials are never read. `.modelos-secure/sent.jsonl` lists what was sent, `--explain` shows the outline and what may and may not be read without sending anything, and `--offline` keeps everything on your machine.
-
-At a terminal, `modelos-secure` on its own starts a session about the app in the folder: ask about it in your own words, and each answer cites the files and lines it rests on, checked against the code.
-
-| Command                                       | Does                                                               |
-| --------------------------------------------- | ------------------------------------------------------------------ |
-| `modelos-secure`                              | At a terminal, a session about the app in this folder.             |
-| `modelos-secure login`                        | Saves a workspace token, and signs in with Google if needed.       |
-| `modelos-secure scan .`                       | Connects this repository. `--offline`, `--explain`, `--yes`.       |
-| `modelos-secure review`                       | Starts a review of this system. `--quick`, `--ci`, `--budget`.     |
-| `modelos-secure replay F-031`                 | Replays one finding.                                               |
-| `modelos-secure doctor`                       | Checks the setup and fixes what it can.                            |
-| `modelos-secure runner`                       | Serves a review's attempts from this machine, in the app's folder. |
-| `modelos-secure export R-1179 --format sarif` | Writes a review's findings as SARIF or JSON.                       |
-| `modelos-secure --version`                    | Prints this CLI's version.                                         |
-
-A review of an app connected by the scan reaches it through a runner on the machine that runs it. `modelos-secure review` starts one itself, and keeps it while the review is paused; a review started from the app needs `modelos-secure runner` running in the app's folder, and says so if none is. A start command is checked before it runs and saved only once the app has started with it.
-
-During a review, actions are held and never run. Outside a review the hooks do nothing. Requires Node 22 or newer. Python apps need Python 3.10 or newer.
-
-Every command says what it takes with `--help`, such as `modelos-secure scan --help`, and refuses a flag it does not take.
-
-| Exit code | Means                                                          |
-| --------- | -------------------------------------------------------------- |
-| 0         | Done.                                                          |
-| 1         | Something failed, or a fix check found a break.                |
-| 2         | The command was used wrongly.                                  |
-| 3         | There are questions only a person can answer, as `--ci` lists. |
-| 130       | Stopped with Ctrl-C. What was done is kept.                    |
-
-## Signing in
-
-Copy the login command from the workspace tokens page in the app. It has the app's address and, when the app is behind Google sign-in, the Google client to sign in with:
-
-```bash
-npx modelos-secure login --url <address> --client-id <client ID> --client-secret <client secret>
-```
-
-Paste the workspace token when it asks. The token is never typed on the command line. Your browser then opens for you to sign in with Google. The address, the token and the Google sign-in are kept in `~/.modelos-secure/credentials.json`, readable only by you, and the sign-in is renewed as it runs out. Without `--client-id`, as on a local stack, there is no Google sign-in.
-
-When the app is reached at an IP address and its certificate is issued for a name, the login command also has `--tls-name` and that name. The CLI then connects to the address and checks the certificate against the name: its chain, its dates and the name are all still checked. `MODELOS_SECURE_TLS_NAME` does the same for one run. When something cannot be reached, the CLI says why in plain words.
-
-`MODELOS_SECURE_URL` and `MODELOS_SECURE_TOKEN` take the place of the saved address and token. `modelos-secure doctor` says who is signed in to Google, and why a request was turned away.
-
-## In CI
-
-CI has no browser, so it signs in to Google as a service account. The service account needs IAP-secured Web App User on the app, and the client ID must be the one on the tokens page. Set `MODELOS_SECURE_URL` and `MODELOS_SECURE_TOKEN`, then one of these:
-
-- `MODELOS_SECURE_CLIENT_ID`, the client ID from the tokens page, with gcloud signed in as the service account. The CLI runs `gcloud auth print-identity-token --audiences=<client ID>` and runs it again as the token runs out, so it suits reviews of any length. It does not work with a person's own gcloud sign-in.
-- `MODELOS_SECURE_IAP_TOKEN`, an ID token for the service account with the client ID as its audience. It is sent as it is and never renewed, and it lasts about an hour. In GitHub Actions, `google-github-actions/auth` makes one with `token_format: id_token`, `id_token_audience` set to the client ID and `id_token_include_email: true`.

package/dist/package.json

@@ -1,20 +0,0 @@
-{
-  "name": "modelos-secure",
-  "version": "0.3.0",
-  "description": "Tests AI systems for Security, Safety and Quality. One command connects a system from its code.",
-  "license": "UNLICENSED",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/mn-chetan/modelos-secure.git"
-  },
-  "type": "module",
-  "bin": {
-    "modelos-secure": "cli.js"
-  },
-  "exports": {
-    "./hook": "./hook/hook.mjs"
-  },
-  "engines": {
-    "node": ">=20"
-  }
-}