@bazel/typescript 2.3.1

TypeScript rules for Bazel

@bazel/typescript@2.3.1 was published on 2020-11-24. Its manifest declares 4 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: No longer maintained, https://github.com/aspect-build/rules_ts is the recommended replacement

All @bazel/typescript versions · Permanent reference to 2.3.1 · Latest release

Package specifications

Version2.3.1
License declarationApache-2.0
Published2020-11-24T23:12:26.527Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size19089.68 KiB
Published file count104
Package typeNot declared
ES module entryNot declared
Default entry./internal/tsc_wrapped/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies20
Repository stars763
Repository forks529

Install @bazel/typescript 2.3.1

npm install @bazel/typescript@2.3.1
pnpm add @bazel/typescript@2.3.1
yarn add @bazel/typescript@2.3.1

Runtime dependencies

Peer requirements

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-Review9/10 — Found 26/27 approved changesets -- score normalized to 9
Maintained5/10 — 6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies1/10 — dependency not pinned by hash detected -- score normalized to 1
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Signed-Releases10/10 — 4 out of the last 4 releases have a total of 4 signed artifacts.
Security-Policy0/10 — security policy file not detected
SAST5/10 — SAST tool is not run on all commits -- score normalized to 5

Evidence and freshness