ts-mocha 9.0.0-alpha1

Mocha thin wrapper that allows running TypeScript tests with TypeScript runtime (ts-node) to get rid of compilation complexity

ts-mocha@9.0.0-alpha1 was published on 2020-10-25. Its manifest declares 2 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=10.0.0.

All ts-mocha versions · Permanent reference to 9.0.0-alpha1 · View npm registry JSON · Latest release

Package specifications

Version9.0.0-alpha1
License declarationMIT
Published2020-10-25T11:57:31.782Z
Node.js requirement>=10.0.0
Type declarationsNot declared
Runtime dependency count2
Peer requirement count1
Optional dependency count1
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size71.42 KiB
Published file count7
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies13
Repository stars196
Repository forks27

Install ts-mocha 9.0.0-alpha1

npm install ts-mocha@9.0.0-alpha1
pnpm add ts-mocha@9.0.0-alpha1
yarn add ts-mocha@9.0.0-alpha1

Runtime dependencies

Peer requirements

  • mocha ^3.X.X || ^4.X.X || ^5.X.X || ^6.X.X || ^7.X.X || ^8.X.X

Optional dependencies

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-Review2/10 — Found 7/30 approved changesets -- score normalized to 2
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness