traceviewer 1.0.11

Trace-Viewer is the javascript frontend for Chrome about:tracing and Android systrace.

traceviewer@1.0.11 was published on 2016-05-09. 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 traceviewer versions · Permanent reference to 1.0.11 · View npm registry JSON · Latest release

Package specifications

Version1.0.11
License declarationBSD-2-Clause
Published2016-05-09T22:44:16.250Z
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 sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrytracing/tracing/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars1965
Repository forks565

Install traceviewer 1.0.11

npm install traceviewer@1.0.11
pnpm add traceviewer@1.0.11
yarn add traceviewer@1.0.11

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-Review10/10 — all changesets reviewed
    Maintained0/10 — project is archived
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    SAST0/10 — no SAST tool detected
    License10/10 — license file detected
    Security-Policy0/10 — security policy file not detected
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    Binary-Artifacts0/10 — binaries present in source code
    Fuzzing10/10 — project is fuzzed
    Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4

    Evidence and freshness