@aws-amplify/geo

Geo category for aws-amplify

@aws-amplify/geo@3.1.0 was published on 2026-09-21. Its manifest declares 5 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @aws-amplify/geo versions · Permanent reference to 3.1.0

Package specifications

Version3.1.0
License declarationApache-2.0
Published2026-09-21T10:02:41.547Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count5
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size292.58 KiB
Published file count51
Package typeNot declared
ES module entry./dist/esm/index.mjs
Default entry./dist/cjs/index.js
Side effects declaration["./dist/cjs/geo/geo.js","./dist/esm/geo/geo.mjs"]
Direct advisories0
Resolved graph dependencies31
Repository stars9555
Repository forks2173

Install @aws-amplify/geo 3.1.0

npm install @aws-amplify/geo@3.1.0
pnpm add @aws-amplify/geo@3.1.0
yarn add @aws-amplify/geo@3.1.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.

Maintained10/10 — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Code-Review9/10 — Found 20/22 approved changesets -- score normalized to 9
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Binary-Artifacts4/10 — binaries present in source code
Pinned-Dependencies7/10 — dependency not pinned by hash detected -- score normalized to 7
Branch-Protection10/10 — branch protection is fully enabled on development and all release branches
Security-Policy10/10 — security policy file detected
Fuzzing0/10 — project is not fuzzed
SAST10/10 — SAST tool detected

Evidence and freshness