@code-hike/classer 0.3.0-next.5

> Classer is a tool from [Code Hike](https://codehike.org)

@code-hike/classer@0.3.0-next.5 was published on 2021-03-25. Its manifest declares 0 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.

All @code-hike/classer versions · Permanent reference to 0.3.0-next.5 · Latest release

Package specifications

Version0.3.0-next.5
License declarationMIT
Published2021-03-25T03:49:05.291Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size10.12 KiB
Published file count6
Package typeNot declared
ES module entrydist/index.esm.js
Default entrydist/index.cjs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars5396
Repository forks168

Install @code-hike/classer 0.3.0-next.5

npm install @code-hike/classer@0.3.0-next.5
pnpm add @code-hike/classer@0.3.0-next.5
yarn add @code-hike/classer@0.3.0-next.5

Runtime dependencies

  • None declared

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.

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

    Evidence and freshness