@types/yaml 1.0.0

TypeScript definitions for yaml

@types/yaml@1.0.0 was published on 2018-09-21. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @types/yaml versions · Permanent reference to 1.0.0 · Latest release

Package specifications

Version1.0.0
License declarationMIT
Published2018-09-21T18:09:39.572Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size21.31 KiB
Published file count12
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars1701
Repository forks186

Install @types/yaml 1.0.0

npm install @types/yaml@1.0.0
pnpm add @types/yaml@1.0.0
yarn add @types/yaml@1.0.0

Runtime dependencies

  • None declared

Peer requirements

  • None declared

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

    Evidence and freshness