@scovant/core 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Scovant
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,75 @@
+# @scovant/core
+
+A thin `npm` launcher for [`scovant-core`](https://pypi.org/project/scovant-core/), the
+passive AI-agent-readiness scanner. This package contains no scanning logic of its own —
+running `scovant` from Node just finds a way to run the real Python engine and execs it,
+forwarding your arguments and its exit code unchanged.
+
+## Usage
+
+```sh
+npx @scovant/core scan https://example.com
+```
+
+or install it globally:
+
+```sh
+npm install -g @scovant/core
+scovant scan https://example.com --format json
+```
+
+## How it works
+
+On each run, the launcher looks for a way to run the Python package `scovant-core`
+(requires Python >= 3.12), in order:
+
+1. [`uv`](https://docs.astral.sh/uv/) via `uvx --from scovant-core==<version> scovant`
+2. [`pipx`](https://pipx.pypa.io/) via `pipx run --spec scovant-core==<version> scovant`
+3. a `python3` on `PATH` that already has `scovant_core` installed, via `python3 -m scovant_core`
+
+If none of those are available, it exits with code `9` and prints instructions for
+installing one of them. Any other exit code is the underlying `scovant-core` engine's own
+— see its documentation for the exit-code contract (0-5).
+
+The first two paths pin the exact version: `npx @scovant/core@X` resolves
+`scovant-core==X`, so you get engine X. **The third path does not** — it runs whatever
+version of `scovant_core` that interpreter happens to have. The launcher checks, and if
+the versions differ it prints a warning naming both and runs anyway (leaving you with a
+working engine beats refusing to start), but scores are only comparable within one ruleset
+version. Install `uv` or `pipx` if you need the pin.
+
+Each candidate is probed before use, and on the first run on a machine that probe includes
+`uvx`/`pipx` downloading the Python package. On a slow link a probe can be killed by its
+own timeout; the launcher says so explicitly (it never reports a slow tool as a missing
+one), and you can raise the budget:
+
+```sh
+SCOVANT_NPM_PROBE_TIMEOUT_MS=300000 npx @scovant/core scan https://example.com
+```
+
+## Platform support
+
+Developed and tested on Linux and macOS. The launcher is POSIX-shaped: it probes for
+executables by name (`uvx`, `pipx`, `python3.13`/`python3.12`/`python3`) and its
+"nothing found" message suggests `python3 -m pip`. On Windows, `uvx`/`pipx` on `PATH` do
+resolve, but a Python installed as `python`/`py` (rather than `python3`) will not be
+found by the third fallback. Windows is not covered by CI, so it is not claimed as
+supported.
+
+## Why a launcher instead of a bundled binary?
+
+`scovant-core` is a Python package; this package exists only so `npx @scovant/core ...`
+works without you needing to already have a Python environment set up for it, provided
+`uv` or `pipx` is available. It has zero npm runtime dependencies and never installs
+anything on its own (no `postinstall`) — the actual engine is fetched on demand by
+whichever runner it finds, and only when you invoke `scovant`.
+
+## Provenance
+
+This npm package carries no build-provenance attestation (npm cannot generate one from a
+private source repository), while the `scovant-core` Python package it fetches from PyPI
+does.
+
+## License
+
+Apache-2.0

package/bin/scovant.js

@@ -0,0 +1,153 @@
+#!/usr/bin/env node
+// backend/scovant-core/npm/bin/scovant.js
+'use strict';
+const { spawnSync } = require('child_process');
+const { statSync } = require('fs');
+const { delimiter, join: pathJoin } = require('path');
+const { version } = require('../package.json');
+
+const SPEC = `scovant-core==${version}`;
+// A probe that resolves the spec (uvx/pipx) may fetch the engine from PyPI
+// on the first run on a machine — see the comment at resolveRunner — which
+// can take much longer than a plain local `--version` call, so those get a
+// longer budget than the cheap local-only probes. Both budgets are
+// overridable: a genuinely slow link is a real case, and the alternative
+// (a killed probe) is reported as "no runner found", which is worse.
+const OVERRIDE_MS = Number.parseInt(process.env.SCOVANT_NPM_PROBE_TIMEOUT_MS || '', 10);
+const HAS_OVERRIDE = Number.isFinite(OVERRIDE_MS) && OVERRIDE_MS > 0;
+const PROBE = { stdio: 'ignore', timeout: HAS_OVERRIDE ? OVERRIDE_MS : 10000 };
+const PROBE_RESOLVE = { stdio: 'ignore', timeout: HAS_OVERRIDE ? OVERRIDE_MS : 60000 };
+// Same budget as PROBE, but keeps stdout so the printed version can be
+// compared with this launcher's own (see checkVersion).
+const PROBE_CAPTURE = {
+  stdio: ['ignore', 'pipe', 'ignore'], encoding: 'utf8', timeout: PROBE.timeout,
+};
+const TESTING = process.env.SCOVANT_NPM_TEST === '1';
+
+// A probe that is killed by its own timeout is NOT the same thing as a
+// missing tool: reporting "install uv" to someone whose uv is installed and
+// merely slow is false. Track the two apart so the no-runner message can.
+let timedOut = false;
+
+function probe(cmd, args, opts = PROBE) {
+  const r = spawnSync(cmd, args, opts);
+  if (r.error && r.error.code === 'ETIMEDOUT') {
+    timedOut = true;
+    return { ok: false, stdout: '' };
+  }
+  return { ok: !r.error && r.status === 0, stdout: r.stdout || '' };
+}
+
+function works(cmd, args, opts = PROBE) {
+  return probe(cmd, args, opts).ok;
+}
+
+// A fake test double doesn't necessarily behave like the real `uvx` when
+// probed with `--version`, so under SCOVANT_NPM_TEST=1 we skip that
+// behavioral check and only verify an executable named `uvx` exists on
+// PATH. Everything downstream (the real invocation) is identical either way.
+function existsOnPath(cmd) {
+  const pathEnv = process.env.PATH || '';
+  for (const dir of pathEnv.split(delimiter)) {
+    if (!dir) continue;
+    try {
+      const st = statSync(pathJoin(dir, cmd));
+      if (st.isFile() && (st.mode & 0o111)) return true;
+    } catch {
+      // not found in this dir; keep looking
+    }
+  }
+  return false;
+}
+
+// `npx @scovant/core@X` must execute engine X. The uvx and pipx paths get
+// that for free — they resolve the pinned SPEC. The `python3 -m
+// scovant_core` path runs whatever that interpreter happens to have, so the
+// guarantee only holds if we check it: parse the version the probe printed
+// and compare. On a mismatch (or an unparseable answer) we still run —
+// leaving a user with a working engine beats refusing to start — but we say
+// so on stderr, naming BOTH versions, because scores are only comparable
+// within one ruleset version and a silent substitution is exactly the
+// failure this check exists to prevent.
+function warnIfVersionDiffers(cmd, stdout) {
+  const m = /scovant-core\s+(\S+)/.exec(stdout || '');
+  const found = m ? m[1] : null;
+  if (found === version) return;
+  const what = found ? `version ${found}` : 'an unknown version';
+  process.stderr.write(
+    `scovant: warning — running ${what} of the scovant-core engine via "${cmd} -m scovant_core", ` +
+    `but this launcher is @scovant/core ${version}.\n` +
+    `Results may use a different ruleset and are not comparable across versions. ` +
+    `Install uv or pipx (or "${cmd} -m pip install \\"${SPEC}\\"") to pin the engine version.\n`);
+}
+
+function resolveRunner() {
+  // Probe exactly what will be run, not just whether the launcher binary
+  // itself exists: if the spec can't be resolved (e.g. yanked/unpublished
+  // version, no network, index unreachable), `uvx`/`pipx` exit with their
+  // OWN 1 or 2 — indistinguishable from the engine's real "threshold
+  // failed" (1) / "invalid input" (2) exit codes. A failed probe here means
+  // exit 9 ("no usable runner"), never a runner that's about to lie about
+  // what its exit code means. This does mean the very first invocation on a
+  // machine pays uvx/pipx's package download during the probe itself.
+  const uvxAvailable = TESTING
+    ? existsOnPath('uvx')
+    : works('uvx', ['--from', SPEC, 'scovant', '--version'], PROBE_RESOLVE);
+  if (uvxAvailable) {
+    return { cmd: 'uvx', pre: ['--from', SPEC, 'scovant'] };
+  }
+  if (works('pipx', ['run', '--spec', SPEC, 'scovant', '--version'], PROBE_RESOLVE)) {
+    return { cmd: 'pipx', pre: ['run', '--spec', SPEC, 'scovant'] };
+  }
+  // Probe exactly what will be run — `-m scovant_core --version` — not just
+  // whether the package can be imported. A package with no `__main__.py`
+  // (or one whose CLI blows up before parsing `--version`) can import fine
+  // and still fail to execute as a module; a probe that only checks import
+  // would hand back a runner that crashes on the real invocation instead of
+  // reporting "no runner found".
+  for (const py of ['python3.13', 'python3.12', 'python3']) {
+    const r = probe(py, ['-m', 'scovant_core', '--version'], PROBE_CAPTURE);
+    if (r.ok) {
+      warnIfVersionDiffers(py, r.stdout);
+      return { cmd: py, pre: ['-m', 'scovant_core'] };
+    }
+  }
+  return null;
+}
+
+const runner = resolveRunner();
+if (!runner) {
+  if (timedOut) {
+    process.stderr.write(
+      `scovant: a runner was found but its probe timed out, so nothing could be started.\n\n` +
+      `This is usually a slow or offline network: uvx/pipx download the Python package\n` +
+      `"scovant-core" the first time you run this, and that happens during the probe.\n` +
+      `Try again (a partial download is cached), or raise the budget:\n` +
+      `  SCOVANT_NPM_PROBE_TIMEOUT_MS=300000 npx @scovant/core ...\n\n` +
+      `Docs: https://github.com/Scovant/scovant-core\n`);
+    process.exit(9);
+  }
+  process.stderr.write(
+    `scovant: no way to run the scanner was found.\n\n` +
+    `This package is a thin launcher; the scanner itself is the Python package\n` +
+    `"scovant-core" (Python >= 3.12). Install ONE of:\n` +
+    `  - uv/uvx (recommended):  https://docs.astral.sh/uv/   then re-run this command\n` +
+    `  - pipx:                  https://pipx.pypa.io/        then re-run this command\n` +
+    `  - the package directly:  python3 -m pip install "${SPEC}"\n\n` +
+    `Docs: https://github.com/Scovant/scovant-core\n`);
+  process.exit(9);
+}
+
+const r = spawnSync(runner.cmd, [...runner.pre, ...process.argv.slice(2)], { stdio: 'inherit' });
+if (r.error) {
+  process.stderr.write(`scovant: failed to start ${runner.cmd}: ${r.error.message}\n`);
+  process.exit(9);
+}
+if (r.signal) {
+  process.exit(128 + (require('os').constants.signals[r.signal] || 0));
+}
+// `status` can be null with no signal and no error (rare, platform-
+// dependent). Exit codes here are a published contract the GitHub Action
+// branches on, so an unresolved child state must never read as "scan
+// passed" — fall back to 9, the launcher's own "could not run" code.
+process.exit(r.status === null || r.status === undefined ? 9 : r.status);

package/package.json

@@ -0,0 +1,32 @@
+{
+  "name": "@scovant/core",
+  "version": "0.1.0",
+  "description": "Passive AI-agent-readiness scanner (thin launcher for the Python package scovant-core)",
+  "bin": {
+    "scovant": "bin/scovant.js"
+  },
+  "files": [
+    "bin",
+    "README.md",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=18"
+  },
+  "license": "Apache-2.0",
+  "publishConfig": {
+    "access": "public"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Scovant/scovant-core.git"
+  },
+  "keywords": [
+    "ai",
+    "agents",
+    "readiness",
+    "scanner",
+    "llms-txt",
+    "mcp"
+  ]
+}