# libyear mit npm installieren

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

## Installation

```sh
sudo av install npm:libyear
```

Weitere Installationsbefehle:

### Portable und Sprach-Paketmanager

- npm (100%):

```sh
npm install -g libyear
```

  Evidenz: local npm package metadata

## Paketfakten

- **Paketschlüssel:** npm:libyear
- **Paketmanager:** npm
- **Paketmanager-Seite:** <https://www.npmjs.com/package/libyear>
- **Version:** 0.9.3
- **Quellzusammenfassung:** A simple measure of software dependency freshness
- **Homepage:** <https://github.com/jdanil/libyear>
- **Repository:** <https://github.com/jdanil/libyear>
- **Upstream-Dokumentation:** <https://github.com/jdanil/libyear>
- **Lizenz:** LGPL-3.0
- **Quellarchiv:** <https://registry.npmjs.org/libyear/-/libyear-0.9.3.tgz>
- **Issue-Tracker:** <https://github.com/jdanil/libyear/issues>
- **Veröffentlicht:** 2025-09-07T09:08:13.726Z
- **Zuletzt aktualisiert:** 2025-09-07T09:08:13.726Z
- **Generiert:** 2026-08-04T22:13:35+00:00

## Executables

- libyear (cli)
- libyear (Alias)

## Abhängigkeiten

- @js-temporal/polyfill
- cosmiconfig
- execa
- lodash-es
- p-limit
- semver
- terminal-link

## Build-Abhängigkeiten

- @commitlint/cli
- @commitlint/config-conventional
- @eslint/js
- @types/lodash-es
- @types/node
- @types/semver
- eslint
- expect
- husky
- lint-staged
- prettier
- pretty-quick
- tslib
- typescript
- typescript-eslint

## Installationsverhalten

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

## Version und Aktualität

- Seite generiert: 2026-08-04
- Manager-Version: 0.9.3
- Manager aktualisiert: 2025-09-07
- lokale Daten: OK
- Upstream-Repository: https://github.com/jdanil/libyear
- notice: The package-manager record has not changed recently.
- Info: No cached GitHub release or tag data was available.

## Sicherheitshinweise

Für libyear 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.9.3
- **Version Count:** 22
- **Maintainers:** jdanil
- **Author:** Joshua David
- **Publisher:** jdanil
- **Engines:** Node: ^20.18 || ^22.8 || >=24
- **Integrity:** sha512-dYm71n+2vJ0Bw6zK/WvYIVZTCqyg/zVjaSKkZsKfYLao4XIT1yyLDxdPi7VfiXpDfz/ODTSxFkUglxlgsr5pOQ==
- **Shasum:** 9789485307516e2fe8443d34907fd0808db496eb
- **Unpacked Size:** 82,489
- **File Count:** 0
- **Created At:** 2020-02-16T00:20:54.677Z
- **Latest Published At:** 2025-09-07T09:08:13.726Z
- **Modified At:** 2025-09-07T09:08:14.108Z


## 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/) - Local package facts share a topical domain. Shared terms: cli, dependency, dependency-management, developer, developer-tools.
- [semantic-release](https://pkg.so/de/npm/semantic-release/) - Local package facts share a topical domain. Shared terms: cli, cosmiconfig, developer, developer-tools, execa.
- [ls-engines](https://pkg.so/de/npm/ls-engines/) - Local package facts share a topical domain. Shared terms: cli, dependency, dependency-management, developer, developer-tools.

## Quellen

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