@morgan-stanley/ts-mocking-bird

A fully type safe mocking, call verification and import replacement library for jasmine and jest

@morgan-stanley/ts-mocking-bird@2.0.0 was published on 2026-03-11. Its manifest declares 1 runtime dependency and 3 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @morgan-stanley/ts-mocking-bird versions · Permanent reference to 2.0.0

Package specifications

Version2.0.0
License declarationApache-2.0
Published2026-03-11T14:15:44.351Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count3
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size167.76 KiB
Published file count57
Package typemodule
ES module entryNot declared
Default entry./dist/main/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars20
Repository forks5

Install @morgan-stanley/ts-mocking-bird 2.0.0

npm install @morgan-stanley/ts-mocking-bird@2.0.0
pnpm add @morgan-stanley/ts-mocking-bird@2.0.0
yarn add @morgan-stanley/ts-mocking-bird@2.0.0

Runtime dependencies

Peer requirements

  • jasmine 2.x || 3.x || 4.x || 5.x || 6.x (optional peer)
  • jest 26.x || 27.x || 28.x || 29.x || 30.x (optional peer)
  • typescript >=4.2

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-Review10/10 — all changesets reviewed
Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies7/10 — dependency not pinned by hash detected -- score normalized to 7
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
SAST10/10 — SAST tool is run on all commits

Evidence and freshness