@node-red/registry 1.0.1

@node-red/registry ====================

@node-red/registry@1.0.1 was published on 2019-10-04. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @node-red/registry versions · Permanent reference to 1.0.1 · Latest release

Package specifications

Version1.0.1
License declarationApache-2.0
Published2019-10-04T10:30:39.755Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size76.11 KiB
Published file count11
Package typeNot declared
ES module entryNot declared
Default entry./lib/index.js
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars23787
Repository forks3969

Install @node-red/registry 1.0.1

npm install @node-red/registry@1.0.1
pnpm add @node-red/registry@1.0.1
yarn add @node-red/registry@1.0.1

Runtime dependencies

Peer requirements

  • None declared

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.

Maintained10/10 — 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Code-Review4/10 — Found 5/12 approved changesets -- score normalized to 4
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
License10/10 — license file detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Fuzzing0/10 — project is not fuzzed

Evidence and freshness