@ember-tooling/classic-build-addon-blueprint

@ember-tooling/classic-build-addon-blueprint@7.3.0 was published on 2026-09-21. Its manifest declares 9 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @ember-tooling/classic-build-addon-blueprint versions · Permanent reference to 7.3.0

Package specifications

Version7.3.0
License declarationMIT
Published2026-09-21T16:32:15.099Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count9
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size19.59 KiB
Published file count16
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies169
Repository stars3235
Repository forks1154

Install @ember-tooling/classic-build-addon-blueprint 7.3.0

npm install @ember-tooling/classic-build-addon-blueprint@7.3.0
pnpm add @ember-tooling/classic-build-addon-blueprint@7.3.0
yarn add @ember-tooling/classic-build-addon-blueprint@7.3.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.

Code-Review8/10 — Found 8/9 approved changesets -- score normalized to 8
Maintained10/10 — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
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
Binary-Artifacts8/10 — binaries present in source code
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Security-Policy0/10 — security policy file not detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Packaging10/10 — packaging workflow detected

Evidence and freshness