devtools-timeline-model 1.0.15
Parse raw trace data into the Chrome DevTools' structured profiling data models
devtools-timeline-model@1.0.15 was published on 2016-03-20. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=5.0.
All devtools-timeline-model versions · Permanent reference to 1.0.15 · Latest release
Package specifications
| Version | 1.0.15 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2016-03-20T03:42:05.740Z |
| Node.js requirement | >=5.0 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 177 |
| Repository forks | 25 |
Install devtools-timeline-model 1.0.15
npm install devtools-timeline-model@1.0.15 pnpm add devtools-timeline-model@1.0.15 yarn add devtools-timeline-model@1.0.15
Runtime dependencies
- call-with-globals 0.1.0
- chrome-devtools-frontend 1.0.382117
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.
- call-with-globals@0.1.0 — direct
- chrome-devtools-frontend@1.0.382117 — direct
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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 0/10 — Found 2/23 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/devtools-timeline-model/1.0.15 — retrieved 2026-10-29T17:27:13.500Z
- https://api.deps.dev/v3/projects/github.com%2Fpaulirish%2Fdevtools-timeline-model — retrieved 2026-10-29T14:55:19.761Z
- https://api.deps.dev/v3/systems/npm/packages/devtools-timeline-model/versions/1.0.15 — retrieved 2026-10-29T17:27:13.990Z
- https://api.deps.dev/v3/systems/npm/packages/devtools-timeline-model/versions/1.0.15:dependencies — retrieved 2026-10-29T17:27:14.042Z