ng-packagr 5.7.1

Compile and package a TypeScript library to Angular Package Format

ng-packagr@5.7.1 was published on 2019-10-29. Its manifest declares 27 runtime dependencies and 4 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All ng-packagr versions · Permanent reference to 5.7.1 · Latest release

Package specifications

Version5.7.1
License declarationMIT
Published2019-10-29T06:52:24.204Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count27
Peer requirement count4
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size481.64 KiB
Published file count181
Package typeNot declared
ES module entryNot declared
Default entry./public_api.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies274
Repository stars1855
Repository forks300

Install ng-packagr 5.7.1

npm install ng-packagr@5.7.1
pnpm add ng-packagr@5.7.1
yarn add ng-packagr@5.7.1

Runtime dependencies

Peer requirements

  • tslib ^1.9.0
  • typescript >=2.7 <3.6
  • @angular/compiler ^6.0.0 || ^7.0.0 || ^8.0.0-beta.0 || ^8.1.0-beta.0 || ^8.2.0-beta.0 || ^8.3.0-beta.0 || ^8.4.0-beta.0 || >=9.0.0-beta < 9
  • @angular/compiler-cli ^6.0.0 || ^7.0.0 || ^8.0.0-beta.0 || ^8.1.0-beta.0 || ^8.2.0-beta.0 || ^8.3.0-beta.0 || ^8.4.0-beta.0 || >=9.0.0-beta < 9

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Known direct advisories

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review0/10 — Found 1/12 approved changesets -- score normalized to 0
Maintained10/10 — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies10/10 — all dependencies are pinned
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
SAST5/10 — SAST tool is not run on all commits -- score normalized to 5

Evidence and freshness