# ls-engines mit npm installieren

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

## Installation

```sh
sudo av install npm:ls-engines
```

Weitere Installationsbefehle:

### Portable und Sprach-Paketmanager

- npm (100%):

```sh
npm install -g ls-engines
```

  Evidenz: local npm package metadata

## Paketfakten

- **Paketschlüssel:** npm:ls-engines
- **Paketmanager:** npm
- **Paketmanager-Seite:** <https://www.npmjs.com/package/ls-engines>
- **Version:** 0.10.1
- **Quellzusammenfassung:** Determine if your dependency graph's stated "engines" criteria is met.
- **Homepage:** <https://github.com/ljharb/ls-engines#readme>
- **Repository:** <https://github.com/ljharb/ls-engines>
- **Upstream-Dokumentation:** <https://github.com/ljharb/ls-engines#readme>
- **Lizenz:** MIT
- **Quellarchiv:** <https://registry.npmjs.org/ls-engines/-/ls-engines-0.10.1.tgz>
- **Issue-Tracker:** <https://github.com/ljharb/ls-engines/issues>
- **Veröffentlicht:** 2026-06-20T06:20:22.706Z
- **Zuletzt aktualisiert:** 2026-06-20T06:20:22.706Z
- **Generiert:** 2026-08-04T22:13:35+00:00

## Executables

- ls-engines (cli)
- ls-engines (Alias)

## Abhängigkeiten

- fast_array_intersect
- get-dep-tree
- get-json
- json-file-plus
- pargs
- semver
- table

## Build-Abhängigkeiten

- @arethetypeswrong/cli
- @ljharb/eslint-config
- @ljharb/tsconfig
- @types/node
- @types/object-inspect
- @types/semver
- auto-changelog
- encoding
- es-value-fixtures
- eslint
- npmignore
- nyc
- object-inspect
- safe-publish-latest
- tape
- typescript

## Installationsverhalten

- Post-install-Hook: nicht definiert
- npm-Lifecycle-Skripte: prepublish
- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-04
- Manager-Version: 0.10.1
- Manager aktualisiert: 2026-06-20
- lokale Daten: OK
- Upstream-Repository: https://github.com/ljharb/ls-engines
- Info: No cached GitHub release or tag data was available.

## Sicherheitshinweise

Für ls-engines wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.


## Details aus der Quelldatenbank

- **Source Database:** npm registry
- **Dist Tags:** Latest: 0.10.1
- **Version Count:** 32
- **Maintainers:** ljharb
- **Author:** Jordan Harband
- **Publisher:** ljharb
- **Engines:** Node: ^22.21 || ^24.12 || >= 25.2, npm: >=8
- **Integrity:** sha512-ZFTbaq3U9ApZQJKDcEHn00T3lESwIBOmXnGrm810u+inGwHXzCxlHTArC8UPhi1dGjARIyJvLNGyPJoQvkHVUw==
- **Shasum:** 65a4f524fefe870ff89ed217cea44dce7b9d0909
- **Unpacked Size:** 84,042
- **File Count:** 0
- **Created At:** 2020-01-30T08:26:11.941Z
- **Latest Published At:** 2026-06-20T06:20:22.706Z
- **Modified At:** 2026-06-20T06:20:22.828Z


## Verwandte Links

- [Package ecosystem packages](https://pkg.so/de/package-ecosystem-tools/) - Matched curated package taxonomy and local package facts.
- [npm-check](https://pkg.so/de/npm/npm-check/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, dependencies, dependency, dependency-management, developer.
- [nmtree](https://pkg.so/de/npm/nmtree/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, dependency, dependency-management, developer, developer-tools.
- [npm-check-updates](https://pkg.so/de/npm/npm-check-updates/) - Both packages work with overlapping file formats or content types. Shared terms: cli, dependencies, dependency, dependency-management, developer.

## Quellen

- pkg.so package database
- package-page enrichment
- package version freshness
- pkgdb category and tag curation
- package relationship graph
- cross-ecosystem install command graph