@aws-cdk/cx-api 2.0.0-rc.12

Cloud executable protocol

@aws-cdk/cx-api@2.0.0-rc.12 was published on 2021-07-19. Its manifest declares 2 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >= 10.13.0 <13 || >=13.7.0.

All @aws-cdk/cx-api versions · Permanent reference to 2.0.0-rc.12 · View npm registry JSON · Latest release

Package specifications

Version2.0.0-rc.12
License declarationApache-2.0
Published2021-07-19T17:36:30.953Z
Node.js requirement>= 10.13.0 <13 || >=13.7.0
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size434.71 KiB
Published file count109
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies8
Repository stars12957
Repository forks4659

Install @aws-cdk/cx-api 2.0.0-rc.12

npm install @aws-cdk/cx-api@2.0.0-rc.12
pnpm add @aws-cdk/cx-api@2.0.0-rc.12
yarn add @aws-cdk/cx-api@2.0.0-rc.12

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.

  • @aws-cdk/cloud-assembly-schema@2.0.0-rc.12 — direct
  • jsonschema@1.4.0 bundled — indirect
  • lru-cache@6.0.0 bundled — indirect
  • semver@7.3.5 bundled — indirect
  • yallist@4.0.0 bundled — indirect
  • lru-cache@6.0.0 bundled — indirect
  • semver@7.3.5 bundled — direct
  • yallist@4.0.0 bundled — indirect

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 2 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow0/10 — dangerous workflow patterns detected
License10/10 — license file detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
Signed-Releases8/10 — 5 out of the last 5 releases have a total of 5 signed artifacts.
Security-Policy10/10 — security policy file detected
Binary-Artifacts0/10 — binaries present in source code
SAST9/10 — SAST tool detected but not run on all commits
Fuzzing10/10 — project is fuzzed

Evidence and freshness