Skip to main content

Jarvis-Forge

Jarvis-Forge is an independent Python package for user-space software environments and command-based acceptance workflows on scientific workstations and HPC systems. Its CLI is jforge.

Forge runs local command suites and preserves their evidence. Its jforge apt command delegates package recipes, dependency resolution, binary-cache reuse and builds to a pinned, user-local Spack installation. Spack is the only package backend; old source installations remain queryable as archived records. Named environments keep private, versioned shell copies in one shared user directory. Managed services, Slurm submission, scientific comparison policies, and the Jarvis forge forwarding command are planned extensions.

Install

Python 3.10 or newer and a POSIX system with Bash are required for execution. Use WSL on Windows. Forge does not depend on Jarvis-HEP.

python3 -m pip install Jarvis-Forge
jforge --version
jforge --help

The distribution name is Jarvis-Forge. For development from a checkout:

python3 -m pip install -e '.[dev]'

Build source and wheel distributions with:

python3 -m build

Try the acceptance workflow

These commands create a private Forge user directory under the current directory and write a smoke-suite YAML. The demo's init also remembers that directory as your default. The demo uses Python only; it does not download software or start services.

jforge --home .forge-home init
jforge example --output smoke.yaml
jforge validate smoke.yaml
jforge plan smoke.yaml
jforge --home .forge-home run smoke.yaml
jforge --home .forge-home run smoke.yaml
jforge --home .forge-home history --suite forge-smoke

Copy the run IDs printed by run or listed by history:

jforge --home .forge-home show <run-id>
jforge --home .forge-home logs <run-id> --step calculate
jforge --home .forge-home compare <older-run-id> <newer-run-id>

Text results use standalone headings and record summaries suitable for SSH terminals. Paths and commands are emitted as complete lines; the terminal may visually wrap them without inserted line breaks. apt update refreshes the selected backend's recipe metadata. Full structured fields remain available with --json.

--json, --home and --debug work before or after the command. --json emits one JSON object on stdout, while progress goes to stderr. compare --check fails on changed, missing, corrupted or unsuccessful evidence; ordinary comparison only describes differences. Comparison uses exact artifact bytes; scientific equivalence and performance regression policies remain outside the current comparison mode.

Automatic package environment (Bash and Zsh)

A child process cannot change its parent shell. Enable the shell integration once in each interactive session:

eval "$(command jforge apt shell-init)"

Add that line to your own ~/.bashrc or ~/.zshrc to enable it for future shells. The hook sources the selected package environment on startup and refreshes it after successful installs, upgrades, removals and source switches. It uses the selected Forge home, including an explicit --home. Forge does not edit your startup files. Existing shells need to enable the hook themselves. Source switching removes previous managed package paths and restores exported values while preserving user PATH additions. After upgrading Forge, reload this hook once in existing shells to obtain its new behavior; other already-open shells keep their current environment until refreshed. The hook is intended for interactive use, not JSON or script automation.

Spack package names are cached during import/update. Listings read that local cache without starting Spack or accessing the network; complete distribution listings are printed as compact lines. apt list --installed shows one row per package, with version, requested/dependency kind and state. Requested packages appear first, followed by dependencies, sorted by name. Use apt show <package> for full installation paths and instance metadata, or --json for complete records. Installation summaries show selected roots and the dependency count; apt check shows the complete plan. jforge list also includes saved installation instances.

User directories and package queries

Forge uses ~/.jarvis-forge until you choose a default with init. jforge init --home /data/my-forge initializes that directory and remembers it for later commands, including commands started in other terminals and Python environments. Home selection follows --home, JFORGE_HOME, the remembered default, then ~/.jarvis-forge, in that order. Using --home with another command only overrides that invocation.

The remembered location is stored in ~/.config/jarvis-forge/default-home.json, or under an absolute XDG_CONFIG_HOME when configured. jforge paths shows both the selected data directory and this preference file. Initialization does not move existing software or histories. paths, doctor, list, info, validate, plan, history, show and logs do not initialize a user directory or install software.

jforge init --home /data/my-forge
jforge env list
jforge apt list

Both queries above use /data/my-forge without repeating --home, provided no JFORGE_HOME override is set. Repeating init --home with another directory changes the remembered default. A missing remembered directory remains selected; Forge does not silently switch to a different store. To repair a corrupt preference, explicitly initialize the desired directory again.

jforge paths
jforge doctor
jforge doctor --shell /path/to/cbs-env.sh
jforge doctor --shell /path/to/cbs-env.sh --json
jforge list
jforge info eigen
jforge info eigen --package-version 3.4.0 --instance <install-id> --path

info queries JSON installation manifests under the selected package environment's packages/<name>/<version>/<install-id>/manifest.json. jforge apt install creates those records after installation checks pass. Multiple instances are listed explicitly; --path requires a unique match. --package-version selects installed software; --version remains Forge's version query.

New Spack environments install each package into <home>/apps/<profile>/<package>, for example apps/root-env/eigen. These are real installation directories. Versions, compiler/variant/dependency identities and full hashes remain in Spack's own .spack/spec.json and database. There is no extra link layer or Forge-specific package metadata format.

Each new environment permits one locally required build per package name. Forge uses Spack's installer dependency traversal: installed packages do not require their historical build tools again, and binary-only installs require link/run dependencies. In these environments, --cache auto first attempts a validated binary-only install. If packages remain uninstalled, Forge validates the remaining dependencies again, installs each one that has a binary without that package's build tools, and builds the packages that have no binary. --cache only never falls back; --cache never validates source dependencies directly. Real duplicate-name requirements and occupied directories belonging to another build still stop installation. External packages do not compete for managed store directories. Spack validates native metadata; reinstall retains explicit same-spec overwrite behavior and includes build tools when rebuilding.

Operations save the complete concrete graph in dag.json and the initial required dependency plan in plan.json, including its cache_policy. A source fallback saves its refreshed plan in source-plan.json. apt check uses the same initial plan without installing anything; with automatic caching in a package-name environment, its note and JSON source_fallback_requires_validation field identify the conditional source fallback.

Existing environments retain their original layout and multi-instance policy, including when regenerating configuration or selecting another Python. To adopt package-name directories with an existing Forge home, choose a previously unused environment name:

jforge apt switch                         # List saved package environments.
jforge apt switch spack --name root-env    # Create/select this independent package environment.
jforge apt install libeigen3-dev libgsl-dev sqlite3
jforge info eigen --path

jforge paths reports the selected native store. Old prefixes and installed ROOT references are preserved. Each build dependency profile follows the same one-build-per-name rule when newly created. Saved Spack environment revisions are installation history, distinct from the user-selected apt profiles; named shell environments are listed separately by jforge env list.

You select and prepare Python environments with pyenv or your existing tools. doctor --shell sources your trusted Bash script and reports the resulting CC/CXX/FC selections, compiler and build-tool paths and versions, Python interpreter paths and versions, virtual environment prefixes, installed Python packages, and selected module/pyenv variables. It does not choose an environment or switch to a fallback. Without --shell, it inspects the inherited environment. Missing tools and failed version probes are reported individually; activation errors fail the command. --timeout limits the complete inspection, including activation. Shell output is kept separate from JSON results. Inspection creates no Forge user state.

Named shell environments

All Forge installations for the same user share the remembered data directory, independently of the Python version running the CLI; the initial fallback is ~/.jarvis-forge. JFORGE_HOME and --home can explicitly override it. Target Python environments do not need Forge installed.

jforge env add cbs --shell /path/to/cbs-env.sh
jforge env list
jforge env show cbs
jforge env show cbs --path
jforge doctor --env cbs
jforge run acceptance.yaml --env cbs

env add copies the script into environments/<name>/revisions/<revision>/source.sh and generates activate.sh. It checks Bash syntax without sourcing the script. Select Python in your shell or in the registered script using pyenv or your existing tools. Choose a profile explicitly with --env, environment.name in YAML, or source "$(jforge env show cbs --path)" in your own shell.

Each env add ... --replace saves a new revision. Use env show cbs --revision <revision> to inspect a retained revision. If a retained revision contains a Forge Python override, select Python in your shell and re-register the script with --replace. Runs archive the selected revision and its script. The reserved apt environment appears in the list after package activation and remains managed by jforge apt.

Scripts are copied, not relocated together with their dependencies: use stable absolute paths for external files. If the original script changes, register the update with env add cbs --shell /path/to/cbs-env.sh --replace. For reproducibility, files in published revisions are not intended for direct editing. Full usage and storage details are in the environment guide.

User-local packages with Spack

All package operations use Spack. Native Spack extension recipes are downloaded from a dedicated recipe Release and refreshed with apt update, independently of Python package releases. Existing source installations are retained as read-only history; the first package write prepares the default Spack profile:

jforge apt import spack
# Or prepare and select a named package environment:
jforge apt switch spack --name gambit
jforge apt compilers
jforge apt compilers --find
jforge apt list
jforge apt search eigen
jforge apt show libgsl-dev
jforge apt check sqlite3 libgsl-dev libeigen3-dev
jforge apt install sqlite3 libgsl-dev libeigen3-dev --jobs 4
jforge apt list --installed
jforge info libgsl-dev --path

Maintainers publish all package recipes, project build YAMLs, library cards and companion scripts with one standalone command: ./jfrecipes <recipe-revision>. --dry prepares and checks both catalogs without network access. The script needs Python, PyYAML and an authenticated GitHub CLI; it does not import Forge or read its version. Compatibility comes from recipes/release.json and builds/release.json. The fixed recipes/recipes.json and builds/builds.json download entries remain unchanged across recipe and client releases. Clients refresh them with jforge apt update and jforge build update, respectively. See the recipe publishing guide.

import spack selects spack-default. switch spack --name NAME selects a separate store, configuration and saved environments under the shared Forge home. Re-selecting an existing environment retains its configuration and installations. Select Python before creating a profile. Forge registers the active interpreter as an external Spack dependency and keeps it for the life of the profile. A package plan that requires a Spack-managed interpreter or virtual environment is rejected. The interpreter running Forge executes Spack itself. Select compilers/variants explicitly with native quoted specs when needed:

jforge apt install 'gsl@2.8 %gcc@13' 'hdf5~mpi' 'root +python'
jforge apt install sqlite3 --cache only
jforge apt sources
jforge apt sources --add site --url https://example.org/spack-cache
jforge apt sources --trust-key /path/to/site-signing-key.asc
jforge apt update
jforge apt upgrade
jforge apt remove sqlite3 --yes
jforge apt switch

Common Debian development names are aliases to Spack names, for example libgsl-dev → gsl, libeigen3-dev → eigen, and sqlite3 → sqlite. Native Spack specs and name=version are accepted. This does not import Ubuntu/Debian binary packages: Spack owns the dependency graph and uses its own recipes and signed build caches. Search/list use cached package names; show fetches detailed metadata from the managed local Spack installation.

Spack 1.2.2 and an engine-compatible recipe commit are bootstrapped from checksum-pinned official archives, without Git checkouts. Import requires HTTPS access, curl/wget, Bash, and a working Python. Source builds require a usable host compiler and relevant platform tools. The solver may bootstrap into the managed directory. Spack normally uses the host glibc; Forge does not build glibc or promise an isolated Ubuntu user space. AlmaLinux users use a compiler module or Spack compiler package as appropriate for their site.

--cache auto reuses compatible binaries and permits source builds; only refuses source builds for requested packages/dependencies; never requires source builds. Spack's own solver/tool bootstrap is separate. Official cache signing keys are installed from the named official mirror. Custom binary mirrors require the user's trusted key; signature checking stays enabled. Cache availability depends on OS, architecture, compiler and the exact dependency graph. Public cache availability is not guaranteed.

If a plan conflicts with an installed gcc-runtime in a one-build-per-package store, Forge retries resolution against that runtime and checks the new plan before installation. Compatible binaries remain eligible for installation.

Each successful operation saves the concrete spack.lock, a configuration snapshot, package hashes and prefixes, stdout/stderr logs, and a new activation revision. Forge commits the selected environment only after Spack reports its packages installed. A failure retains the previous selection and logs; successful dependencies may remain in the store for reuse. Spack commands run with noninteractive input so detached processes do not access the calling SSH terminal.

APT shows concise progress and results by default. Interactive terminals display phase and package progress bars; pipes, --json, dumb terminals and NO_COLOR use plain phase lines. Package counters follow Spack's reported completions, rather than estimating build percentages. Use jforge apt install eigen --verbose to stream the complete dependency tree, native Spack commands and raw output; --debug also enables detail. These options work before or after commands. Original output is always archived, including the complete tree in command-dependency-tree.stdout.log. Errors retain complete messages and copyable paths without shortened duplicate summaries. --json keeps stdout to one result object and sends progress/detail to stderr.

apt check concretizes and archives a dependency plan without building packages or changing the selected environment; it is not a package integrity audit or a project acceptance test. --dry-run is an offline request preview without solver execution. upgrade re-solves all selected roots against current recipes; change one root with install SPEC. list --upgradable is unavailable because upgrades require solving the environment. reinstall uses Spack's overwrite semantics for the same hash and can change files used by saved revisions.

remove drops explicit roots from the selected environment and retains the store and previous revisions. autoremove --yes delegates garbage collection to Spack while retaining all saved named environments and their build dependencies. It therefore does not reclaim packages still needed by historical revisions. Neither command removes external pyenv/system packages.

The Ubuntu/Debian source resolver, source-package importer, custom build adapters and YAML package recipes have been removed. apt import ubuntu/debian, apt switch ubuntu/debian/legacy, and their source-specific options no longer activate a backend. apt sources now manages Spack mirrors, and apt edit-sources displays those mirrors.

Existing source prefixes, manifests, shell files and operation logs stay on disk without conversion or automatic deletion. An old source selection routes package commands to spack-default; a successful write saves the new selection. Query old records explicitly:

jforge list --archived
jforge info libgsl-dev --archived --path
jforge apt list --archived
jforge apt switch --archived

Archive queries read records without running old shell or recipe commands. Archived records do not satisfy Spack dependencies and cannot be upgraded or removed by the package CLI. Reinstall the packages you need with Spack. Use apt switch spack --direct to select an existing root-level Spack store that uses external Python. Reload apt shell-init once after upgrading; subsequent successful package changes automatically refresh the current shell.

See APT usage, backend design, and compatibility.

Project builds and regression checker

jforge build prepares, configures, compiles, installs and verifies software projects using CMake and reusable installation outputs. The workflow command namespace is reserved for future orchestration design. It is parallel to apt. Recipe dependencies install into the active apt Spack environment; with no apt switch, that environment is spack-default. Build YAML sources are distributed independently from PyPI through GitHub Release assets. From a development checkout:

jforge build validate builds/root-build.yaml
jforge build plan builds/root-build.yaml --env hep
jforge build run builds/root-build.yaml --env hep --jobs 8
jforge build resume <run-id> --jobs 8
jforge build artifacts
source "$(jforge build env <artifact-id> --path)"

A downloaded recipe can own its complete project workspace (after the maintainer publishes the build Release):

jforge build run root-build --directory "$HOME/workshops/root-forge" --jobs 8
source "$HOME/workshops/root-forge/activate.sh"

To inspect or edit the recipe first:

jforge build fetch root-build --directory "$HOME/workshops/root-forge"
jforge build run "$HOME/workshops/root-forge" --jobs 8

The directory contains build.yaml, companion scripts and instances/<name>/{downloads,sources,build,install}. A build with one exported package uses its package and version as the instance name, for example ROOT-6.40.04. Other builds use the recipe ID. Distinct build identities with the same name get a numbered suffix. Each new instance records its full identity in .jforge-instance.json. Resume and reuse also support existing directories named by their full hash.

Package dependencies live in Forge's shared Spack profiles. runs/<run-id> links to the retained Forge history. A successful acceptance run updates the workspace's activate.sh, and a failure leaves the previous successful activation available. Absolute installation paths may be embedded in binaries and build files. Building in a new workspace gives an existing project a new installation path.

In an interactive terminal, build run and build resume show a progress bar while downloading a source archive. The bar shows the bytes transferred and a percentage when the downloader knows the total size. Raw downloader output stays in the run logs. --verbose prints the download log path.

An uncached Release ID is downloaded on explicit build fetch/run; cached IDs and existing workspaces remain usable offline. build update refreshes the catalog explicitly and never overwrites an editable workspace. The existing fetch --output file.yaml still copies only an editable card and its companion scripts; it does not create a workspace. validate/plan stay read-only and do not implicitly download missing recipes.

Build cards use native Forge project sections: dependencies, build and checks. The ROOT card explicitly lists its source URL/checksum, packages, CMake options, extra dependency search paths and acceptance commands. A shortened excerpt is:

name: root-build
dependencies: [gsl, openblas+shared, openssl, libbsd, libmd]  # Full list in the actual card.
build:
  name: ROOT
  version: "6.40.04"
  # The actual card declares source URL, SHA-256 and archive subdirectory here.
  cmake:
    options:
      CMAKE_CXX_STANDARD: 17
      all: true
      fcgi: false
      cuda: false
    includes: [libbsd, mesa-glu, fontconfig]
    libraries: [libbsd, libmd, mesa-glu]
    runtime: [openssl, libbsd, libmd]
checks:
  before:
    python:
      version: ">=3.10"
      development: true
      modules: [numpy]
    tools: [cmake, cc, c++, gfortran]
  after:
    python:
      modules: [ROOT]
    scripts:
      - path: scripts/root_acceptance.py
        args: ["${path}", "${build.version}", "${parameters.cxx_standard}", "${build.features}"]

Only engine policy is implicit: Forge home selection, work/build/install/log directories, phase defaults, ordinary build type and timeouts. These defaults live in card/build_default.yaml; process-log layout lives in card/logging.yaml. Dependency path lists resolve from selected apt package prefixes. Includes/libraries feed both CMake discovery and compiler/linker search paths, including nested builds. Runtime paths apply during builds and after installation, with CMake RPATH defaults. Each CMake step saves resolved paths in dependency-paths.json. The independently released builds/root-build.yaml declares the project requirements; its companion builds/scripts/root_acceptance.py implements ROOT-specific acceptance. build show summarizes the recipe. --expanded adds the resolved steps, and --json prints the card data.

build.source accepts a local source directory or URL/SHA-256/subdir mapping. Use build.cmake.preset for a project's native preset, and requires to consume another build's installation output. Standard checks.before/after declare Python versions/development files, imported modules and executable requirements. Module/tool mappings add constraints, for example modules: {numpy: ">=1.26"}. Checks run with the selected Python, which does not need Forge installed. Reports preserve actual versions, paths and failures in checks.json. Custom Python belongs in relative companion scripts, with optional argument lists; shell strings, cmd/cwd mappings and literal argv lists remain supported. Previous LibDeps/Calculators spellings remain compatible aliases; new cards do not require HEP-specific keys. Similar log presentation does not add a dependency on Jarvis-HEP.

hep is a user-registered environment; omit --env to inherit the current compiler/Python selection. The ROOT recipe currently targets Linux, needs an existing CMake/C/C++/Fortran toolchain and Python with NumPy/development headers, and defaults to C++17. Select the interpreter with pyenv or your shell before running the recipe. ROOT uses the interpreter, headers and library verified in preflight. It configures ROOT with -Dall=ON and turns off fcgi, dcache, R, Qt6Web, CUDA, and the GPU TMVA options. Acceptance requires the declared features, PyROOT, histogram and file I/O, and RooFit. -Dall=ON can build bundled XRootD, VDT, Clad, and RooFit MultiProcess when those packages are not already installed. It does not promise GPU support. ROOT's full real build requires separate target-machine validation of this new automation.

User cards declare prerequisite modules with required_modules; the expanded execution schema represents external build outputs using requires entries. Compatible installed artifacts are reused; missing ones are built first. Recipes, local source digests, parameters, dependency instances and tool observations are locked. Multiple compatible instances require an explicit artifact binding; incompatible compiler/Python/C++ choices fail before consumer configuration. cmake.project consumes pinned prefixes and verifies the selected package-config path. History/show remain available; logs support qualified step names such as root-build.ROOT.install.

Independent recipe distribution (once the maintainer publishes the assets):

jforge build update
jforge build list
jforge build fetch root-build --output root.yaml
PYTHONPATH=src python3 tools/build_project_assets.py --version r1 --output /tmp/forge-build-release

The asset builder prepares versioned YAML, referenced Python scripts and a checksum index. update validates the whole bundle; fetch copies the YAML and its scripts together, refusing conflicting local files. Script changes alter recipe identity, and resume uses the original script snapshots. Companion scripts should be self-contained. The builder never uploads or modifies jfrel. An unavailable Release does not prevent executing local or previously cached YAML.

jforge checker runs commands, builds or the same structured standard checks as regression checks. Standard checks use check: {python: {modules: [numpy]}} and run every time by default. Default selection for command/build checks compares declared input globs (including additions/deletions), check configuration, prerequisite signatures and the observed environment with the last successful evidence. It does not infer all software dependencies from Git changes. Checks with external/untracked inputs should use cache: false or be run with --full.

jforge checker list tests/checker.yaml
jforge checker run tests/checker.yaml --full
jforge checker run tests/checker.yaml
jforge checker run tests/checker.yaml --check build-engine
jforge history --suite forge-development
jforge logs <checker-run-id> --step build-engine

The development checker covers all existing local test modules plus ROOT YAML validation. Build checks can run real ROOT/CBS/MadGraph acceptance separately; --full reruns checks but does not erase CMake incremental builds or force successful build artifacts to rebuild. history, show and logs work for both types. Byte/scientific comparison policies for these new run types are not yet part of compare.

Both executors run in the foreground and clean up their child processes on interruption; use tmux for long SSH builds. See the build implementation and design and checker guide.

Acceptance suite format

Suites use schema_version: 1, a stable id, and ordered command steps. Each step chooses either argv or an explicit Bash script, with optional needs, cwd, timeout_seconds, expect_exit_code and required artifacts. Commands and scripts are trusted user code.

The default working directory is the run's shared workspace/. Declared artifacts are relative file paths within the step's working directory; each is copied into the run archive. Supported placeholders are ${python}, ${suite_dir}, ${run_dir}, ${step_dir} and ${input:name}. Inputs are declared as named file paths relative to the suite file and copied before execution.

Use environment.name: cbs to select a registered environment, optionally pinned with environment.revision. A CLI --env explicitly overrides the suite selection and uses the named environment's current revision. Alternatively, environment.shell points to a Bash script, relative to the suite file. These two YAML selections are mutually exclusive. It is snapshotted and sourced before each command, in the same shell. environment.variables supplies string-valued variables. The recorded plan and raw logs may include values supplied by the user; keep credentials out of suite files and command arguments.

The script must initialize your selected environment in a noninteractive Bash; login shell startup files are not loaded. Different suites may select different scripts. For example:

schema_version: 1
id: cbs-environment
environment:
  shell: ./cbs-env.sh
steps:
  - id: python
    argv: [python, --version]

Use python or python3 for the interpreter selected by that script. ${python} always refers to the interpreter running Forge itself, which can be different. Each executed step saves activation.json and includes its environment report in show --step; reports contain actual tool versions and target Python package inventories. Comparisons include these activated environments, so changing a compiler or Python environment is visible even when commands and script contents are unchanged. Missing activation records make the affected comparison not comparable. Version probes do not compile code or establish that dependencies meet a particular project's requirements.

Every run has a new ID and saves configuration, environment observations, actual commands, activation details, logs, exit status, elapsed time, and declared output files. Source code and arbitrary undeclared outputs are not archived automatically. These records support comparison; they are not a complete machine image or automatic source backup. Failed prerequisites block dependent steps; independent steps continue. Foreground execution does not promise survival after SSH disconnection.

Development and integration

python3 -m pytest

The host integration point is jarvis_forge.cli.main(argv, prog="Jarvis forge"); it returns an exit code and owns the single parser. The standalone console script is operational. Jarvis-HEP forwarding is not yet integrated.

The APT comparison and scientific-library support matrix describes GAMBIT/ROOT prerequisite adapters and remaining build limitations. Source-layout recognition is separate from a successful build on the target HPC.

Project design and implementation scope live in Jarvis-Books. CLI behavior follows the Jarvis ecosystem CLI specification.

Recipe sources live in recipes/, separately from the Python distribution. Maintainers build versioned assets with tools/build_recipe_assets.py and publish them to the dedicated recipes Release. See the recipe publishing workflow in Jarvis-Books/Docs/Jarvis-Forge/RELEASING.md.

Metadata

Release files for Jarvis-Forge 1.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for Jarvis-Forge 1.1.6
File Size Uploaded Provenance Actions
jarvis_forge-1.1.6.tar.gz 190.3 kB Without provenance Details for jarvis_forge-1.1.6.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for Jarvis-Forge 1.1.6
File Interpreter ABI Platform Actions
jarvis_forge-1.1.6-py3-none-any.whl Python 3 none any Details for jarvis_forge-1.1.6-py3-none-any.whl

Total release size: 310.9 kB

Release files / jarvis_forge-1.1.6.tar.gz

Download URL jarvis_forge-1.1.6.tar.gz
Size 190.3 kB
Tags Source
SHA-256 checksum
How to use checksums
c608e7e2203d7d5c77bb900c2f582f648e4754cee26fafa1781d854394ede862
BLAKE2b-256 checksum
How to use checksums
86ca474b8ae4b82722a5e2b79ba5b3a264fbe64c6bc49217c68f8ea6a19e1c87
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Release files / jarvis_forge-1.1.6-py3-none-any.whl

Download URL jarvis_forge-1.1.6-py3-none-any.whl
Size 120.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
975e8009346b34d1ca9e21ba9a75f091f1be0efe1f8974e1312c11a3ace921eb
BLAKE2b-256 checksum
How to use checksums
5a61c2fb2c9ca27b49c8a5ae1fb9f8cc93ddd045f8d2e642e415ca51cf6737c1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Security for Jarvis-Forge 1.1.6

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page