@aws-amplify/api 5.3.3

Api category of aws-amplify

@aws-amplify/api@5.3.3 was published on 2023-06-28. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @aws-amplify/api versions · Permanent reference to 5.3.3 · Latest release

Package specifications

Version5.3.3
License declarationApache-2.0
Published2023-06-28T23:43:43.758Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size68.49 KiB
Published file count42
Package typeNot declared
ES module entry./lib-esm/index.js
Default entry./lib/index.js
Side effects declaration["./lib/API.js","./lib-esm/API.js"]
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars9555
Repository forks2173

Install @aws-amplify/api 5.3.3

npm install @aws-amplify/api@5.3.3
pnpm add @aws-amplify/api@5.3.3
yarn add @aws-amplify/api@5.3.3

Runtime dependencies

Peer requirements

  • None declared

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.

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