@reach/component-component 0.17.0

Declarative React Component Definitions

@reach/component-component@0.17.0 was published on 2022-04-20. Its manifest declares 1 runtime dependency and 2 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @reach/component-component versions · Permanent reference to 0.17.0 · Latest release

Package specifications

Version0.17.0
License declarationMIT
Published2022-04-20T05:37:45.751Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count1
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size19.62 KiB
Published file count9
Package typeNot declared
ES module entrydist/reach-component-component.esm.js
Default entrydist/reach-component-component.cjs.js
Side effects declaration["*.css"]
Direct advisories0
Resolved graph dependencies5
Repository stars5963
Repository forks556

Install @reach/component-component 0.17.0

npm install @reach/component-component@0.17.0
pnpm add @reach/component-component@0.17.0
yarn add @reach/component-component@0.17.0

Runtime dependencies

Peer requirements

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.

OpenSSF repository checks

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

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

Evidence and freshness