expect-type 0.20.0-0

[![CI](https://github.com/mmkal/expect-type/actions/workflows/ci.yml/badge.svg)](https://github.com/mmkal/expect-type/actions/workflows/ci.yml) ![npm](https://img.shields.io/npm/dt/expect-type) [![X (formerly Twitter) Follow](https://img.shields.io/twitte

expect-type@0.20.0-0 was published on 2024-08-13. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=12.0.0.

All expect-type versions · Permanent reference to 0.20.0-0 · Latest release

Package specifications

Version0.20.0-0
License declarationApache-2.0
Published2024-08-13T18:11:51.180Z
Node.js requirement>=12.0.0
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size103.11 KiB
Published file count13
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars567
Repository forks11

Install expect-type 0.20.0-0

npm install expect-type@0.20.0-0
pnpm add expect-type@0.20.0-0
yarn add expect-type@0.20.0-0

Runtime dependencies

  • None declared

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained7/10 — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Pinned-Dependencies1/10 — dependency not pinned by hash detected -- score normalized to 1
Code-Review3/10 — Found 10/27 approved changesets -- score normalized to 3
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness