@microsoft/api-extractor 7.8.6
Analyze the exported API for a TypeScript library and generate reviews, documentation, and .d.ts rollups
@microsoft/api-extractor@7.8.6 was published on 2020-05-26. Its manifest declares 9 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 7.8.6 · Latest release
Package specifications
| Version | 7.8.6 |
|---|---|
| License declaration | MIT |
| Published | 2020-05-26T23:00:57.555Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 9 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 1404.52 KiB |
| Published file count | 191 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | Unknown |
| Repository stars | 6500 |
| Repository forks | 714 |
Install @microsoft/api-extractor 7.8.6
npm install @microsoft/api-extractor@7.8.6 pnpm add @microsoft/api-extractor@7.8.6 yarn add @microsoft/api-extractor@7.8.6
Runtime dependencies
- colors ~1.2.1
- lodash ~4.17.15
- resolve 1.8.1
- source-map ~0.6.1
- typescript ~3.7.2
- @microsoft/tsdoc 0.12.19
- @rushstack/ts-command-line 4.4.0
- @rushstack/node-core-library 3.22.1
- @microsoft/api-extractor-model 7.8.4
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.
| Maintained | 10/10 — 30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10 |
|---|---|
| Code-Review | 6/10 — Found 18/26 approved changesets -- score normalized to 6 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Security-Policy | 10/10 — security policy file detected |
| Dangerous-Workflow | 0/10 — dangerous workflow patterns detected |
| License | 9/10 — license file detected |
| Pinned-Dependencies | 6/10 — dependency not pinned by hash detected -- score normalized to 6 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 7/10 — SAST tool is not run on all commits -- score normalized to 7 |
Evidence and freshness
- https://registry.npmjs.org/%40microsoft%2Fapi-extractor/7.8.6 — retrieved 2026-10-29T12:34:02.309Z
- https://api.deps.dev/v3/projects/github.com%2Fmicrosoft%2Frushstack — retrieved 2026-10-29T09:00:17.856Z
- https://api.deps.dev/v3/systems/npm/packages/%40microsoft%2Fapi-extractor/versions/7.8.6 — retrieved 2026-10-29T12:34:03.388Z