uncontrollable 7.0.0

Wrap a controlled react component, to allow specific prop/handler pairs to be uncontrolled

uncontrollable@7.0.0 was published on 2019-06-18. Its manifest declares 2 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All uncontrollable versions · Permanent reference to 7.0.0 · Latest release

Package specifications

Version7.0.0
License declarationMIT
Published2019-06-18T15:04:22.149Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size30.10 KiB
Published file count11
Package typeNot declared
ES module entryesm/index.js
Default entrycjs/index.js
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars203
Repository forks35

Install uncontrollable 7.0.0

npm install uncontrollable@7.0.0
pnpm add uncontrollable@7.0.0
yarn add uncontrollable@7.0.0

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-Review0/10 — Found 2/28 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness