Automic VaultAutomic Vault

brew

jerryscript mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für jerryscript in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install jerryscript

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#jerryscript

nixpkgs package indexes · pkgs/by-name/je/jerryscript/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Ultra-lightweight JavaScript engine for the Internet of Things

Verlauf

Projektgeschichte und Nutzung

JerryScript is a lightweight JavaScript engine for constrained Internet of Things devices. The project site and README emphasize microcontroller-class memory budgets, C99 portability, on-device compilation and execution, bytecode snapshots, and an embeddable C API.

Projektgeschichte

The public GitHub repository dates to 2015. The project presented itself early as a JavaScript engine for devices with less than 64 KB of RAM and less than 200 KB of flash, targeting a niche that mainstream browser and server JavaScript engines did not fit.

JerryScript reached a 1.0 GitHub release in 2016 and continued through the 2.x and 3.x release lines. Later release notes show the project expanding beyond its original ECMAScript 5.1 baseline, while still tracking footprint and conformance as central engineering constraints.

Adoptionsgeschichte

JerryScript gained ecosystem legitimacy by becoming an OpenJS Foundation hosted project. The OpenJS project listing describes it as a fully featured JavaScript engine for IoT devices, and the JerryScript site links it with IoT.js, a related JavaScript platform for IoT applications.

Package-manager adoption through Homebrew and Nix gives developers a straightforward way to build and experiment with the `jerry` command-line engine on workstations, even though the project's natural deployment target is embedded firmware and constrained devices.

Wie es verwendet wird

The repository documents a simple source build with `python tools/build.py`, producing the `jerry` executable. Library users embed the engine through its C API, while the snapshot mechanism allows JavaScript source to be precompiled to bytecode before deployment.

Warum Paket-Nerds sich dafür interessieren

JerryScript is interesting to package people because it is not another desktop JavaScript runtime. It packages a tiny embeddable engine whose constraints are closer to firmware than Node.js, making it a useful test case for how package managers expose embedded-runtime tooling to general-purpose developer machines.

Zeitleiste

  • 2015: Public GitHub repository created for jerryscript-project/jerryscript.
  • 2016: JerryScript 1.0 released on GitHub.
  • 2019: JerryScript 2.0 released on GitHub.
  • 2024: JerryScript 3.0.0 release notes report broader ECMAScript feature coverage.

Related projects

  • JerryScript is related to IoT.js through the project site's Powering IoT.js link and to the OpenJS Foundation project family through OpenJS hosting.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 8 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
jerrycliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version3.0.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv3.0.0

https://github.com/jerryscript-project/jerryscript

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:jerryscript
Version3.0.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/jerryscript
Homepagehttps://jerryscript.net
Repositoryhttps://github.com/jerryscript-project/jerryscript
Upstream-Dokumentationhttps://github.com/jerryscript-project/jerryscript#readme
LizenzApache-2.0
Quellarchivhttps://github.com/jerryscript-project/jerryscript/archive/refs/tags/v3.0.0.tar.gz
Build-Abhängigkeitencmake
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namejerryscript
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

jerryscript

nix profile install nixpkgs#jerryscript
  • normalized package name match
  • Abgeglichen nach: Jerryscript
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/je/jerryscript/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment