@unimodules/core 2.0.1

Universal modules core

@unimodules/core@2.0.1 was published on 2019-06-05. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: replaced by the 'expo' package, learn more: https://blog.expo.dev/whats-new-in-expo-modules-infrastructure-7a7cdda81ebc

All @unimodules/core versions · Permanent reference to 2.0.1 · Latest release

Package specifications

Version2.0.1
License declarationMIT
Published2019-06-05T23:40:30.491Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size118.00 KiB
Published file count96
Package typeNot declared
ES module entryNot declared
Default entrybuild/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies1
Repository stars52895
Repository forks14690

Install @unimodules/core 2.0.1

npm install @unimodules/core@2.0.1
pnpm add @unimodules/core@2.0.1
yarn add @unimodules/core@2.0.1

Runtime dependencies

Peer requirements

  • None declared

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.

Maintained10/10 — 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Code-Review9/10 — Found 29/30 approved changesets -- score normalized to 9
Security-Policy4/10 — security policy file detected
License10/10 — license file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts0/10 — binaries present in source code
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness