@microsoft/api-extractor 4.1.0

Validate, document, and review the exported API for a TypeScript library

@microsoft/api-extractor@4.1.0 was published on 2017-10-20. Its manifest declares 11 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 @microsoft/api-extractor versions · Permanent reference to 4.1.0 · Latest release

Package specifications

Version4.1.0
License declarationMIT
Published2017-10-20T19:57:31.922Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count11
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies32
Repository stars6500
Repository forks714

Install @microsoft/api-extractor 4.1.0

npm install @microsoft/api-extractor@4.1.0
pnpm add @microsoft/api-extractor@4.1.0
yarn add @microsoft/api-extractor@4.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.

Maintained10/10 — 30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
Code-Review6/10 — Found 18/26 approved changesets -- score normalized to 6
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy10/10 — security policy file detected
Dangerous-Workflow0/10 — dangerous workflow patterns detected
License9/10 — license file detected
Pinned-Dependencies6/10 — dependency not pinned by hash detected -- score normalized to 6
Binary-Artifacts10/10 — no binaries found in the repo
Fuzzing0/10 — project is not fuzzed
SAST7/10 — SAST tool is not run on all commits -- score normalized to 7

Evidence and freshness