@react-native-async-storage/async-storage 1.15.0

Asynchronous, persistent, key-value storage system for React Native.

@react-native-async-storage/async-storage@1.15.0 was published on 2021-04-02. Its manifest declares 1 runtime dependency and 2 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @react-native-async-storage/async-storage versions · Permanent reference to 1.15.0 · Latest release

Package specifications

Version1.15.0
License declarationMIT
Published2021-04-02T08:31:41.743Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size388.33 KiB
Published file count86
Package typeNot declared
ES module entrylib/module/index.js
Default entrylib/commonjs/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars5073
Repository forks486

Install @react-native-async-storage/async-storage 1.15.0

npm install @react-native-async-storage/async-storage@1.15.0
pnpm add @react-native-async-storage/async-storage@1.15.0
yarn add @react-native-async-storage/async-storage@1.15.0

Runtime dependencies

Peer requirements

  • react ~16.8.6 || ~16.9.0 || ~16.11.0 || ~16.13.1 || ~17.0.1
  • react-native ^0.60.6 || ^0.61.5 || ^0.62.2 || ^0.63.2 || ^0.64.0 || 1000.0.0

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review3/10 — Found 5/13 approved changesets -- score normalized to 3
Maintained3/10 — 2 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 3
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts8/10 — binaries present in source code
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

Evidence and freshness