gcs-resumable-upload 2.1.0

Upload a file to Google Cloud Storage with built-in resumable behavior

gcs-resumable-upload@2.1.0 was published on 2019-06-19. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.10.0.

Deprecated: gcs-resumable-upload is deprecated. Support will end on 11/01/2023

All gcs-resumable-upload versions · Permanent reference to 2.1.0 · Latest release

Package specifications

Version2.1.0
License declarationMIT
Published2019-06-19T14:34:12.712Z
Node.js requirement>=8.10.0
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size51.22 KiB
Published file count10
Package typeNot declared
ES module entryNot declared
Default entrybuild/src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies61
Repository stars62
Repository forks27

Install gcs-resumable-upload 2.1.0

npm install gcs-resumable-upload@2.1.0
pnpm add gcs-resumable-upload@2.1.0
yarn add gcs-resumable-upload@2.1.0

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.

Maintained0/10 — project is archived
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review10/10 — all changesets reviewed
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness