bem-naming 0.0.1

bem-naming [![NPM version](https://badge.fury.io/js/bem-naming.svg)](http://badge.fury.io/js/bem-naming) [![Build Status](https://travis-ci.org/bem/bem-naming.svg)](https://travis-ci.org/bem/bem-naming) [![Dependency Status](https://gemnasium.com/bem/bem-

bem-naming@0.0.1 was published on 2014-05-12. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.8.0.

All bem-naming versions · Permanent reference to 0.0.1 · Latest release

Package specifications

Version0.0.1
License declarationNot declared
Published2014-05-12T20:51:01.326Z
Node.js requirement>= 0.8.0
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/bem-naming
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars89
Repository forks24

Install bem-naming 0.0.1

npm install bem-naming@0.0.1
pnpm add bem-naming@0.0.1
yarn add bem-naming@0.0.1

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 7/10 approved changesets -- score normalized to 7
    Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Binary-Artifacts10/10 — no binaries found in the repo
    Security-Policy0/10 — security policy file not detected
    License0/10 — license file not detected
    Fuzzing0/10 — project is not fuzzed
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness