chrome-trace-event 1.0.0

A library to create a trace of your node app per Google's Trace Event format.

chrome-trace-event@1.0.0 was published on 2018-04-25. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=6.0.

All chrome-trace-event versions · Permanent reference to 1.0.0 · Latest release

Package specifications

Version1.0.0
License declarationMIT
Published2018-04-25T02:33:27.464Z
Node.js requirement>=6.0
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size25.35 KiB
Published file count12
Package typeNot declared
ES module entryNot declared
Default entry./dist/trace-event.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars30
Repository forks5

Install chrome-trace-event 1.0.0

npm install chrome-trace-event@1.0.0
pnpm add chrome-trace-event@1.0.0
yarn add chrome-trace-event@1.0.0

Runtime dependencies

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.

Binary-Artifacts10/10 — no binaries found in the repo
Code-Review2/10 — Found 3/14 approved changesets -- score normalized to 2
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
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness