@angular/localize 17.0.0-next.6

Angular - library for localizing messages

@angular/localize@17.0.0-next.6 was published on 2023-09-27. Its manifest declares 3 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.13.0.

All @angular/localize versions · Permanent reference to 17.0.0-next.6 · Latest release

Package specifications

Version17.0.0-next.6
License declarationMIT
Published2023-09-27T21:01:20.891Z
Node.js requirement>=18.13.0
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size462.17 KiB
Published file count87
Package typemodule
ES module entry./fesm2022/localize.mjs
Default entryNot declared
Side effects declaration["./esm2022/init/**","./fesm2022/init.mjs"]
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars101102
Repository forks29578

Install @angular/localize 17.0.0-next.6

npm install @angular/localize@17.0.0-next.6
pnpm add @angular/localize@17.0.0-next.6
yarn add @angular/localize@17.0.0-next.6

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

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.

OpenSSF repository checks

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

Code-Review10/10 — all changesets reviewed
Maintained10/10 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
CII-Best-Practices2/10 — badge detected: InProgress
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
License10/10 — license file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Binary-Artifacts10/10 — no binaries found in the repo
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies10/10 — all dependencies are pinned
Fuzzing10/10 — project is fuzzed

Evidence and freshness