stacktracey 1.0.71
Parses call stacks. Reads sources. Clean & filtered output. Sourcemaps. Node & browsers.
stacktracey@1.0.71 was published on 2017-10-10. Its manifest declares 2 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 stacktracey versions · Permanent reference to 1.0.71 · Latest release
Package specifications
| Version | 1.0.71 |
|---|---|
| License declaration | Unlicense |
| Published | 2017-10-10T16:58:54.733Z |
| Node.js requirement | Not declared |
| 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 | stacktracey |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 224 |
| Repository forks | 24 |
Install stacktracey 1.0.71
npm install stacktracey@1.0.71 pnpm add stacktracey@1.0.71 yarn add stacktracey@1.0.71
Runtime dependencies
- as-table ^1.0.31
- get-source ^1.0.21
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.
- as-table@1.0.55 — direct
- data-uri-to-buffer@2.0.2 — indirect
- get-source@1.0.42 — direct
- printable-characters@1.0.42 — indirect
- source-map@0.6.1 — indirect
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 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 0/10 — Found 2/27 approved changesets -- score normalized to 0 |
| 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 | 10/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/stacktracey/1.0.71 — retrieved 2026-10-29T13:19:10.579Z
- https://api.deps.dev/v3/projects/github.com%2Fxpl%2Fstacktracey — retrieved 2026-10-29T12:37:01.233Z
- https://api.deps.dev/v3/systems/npm/packages/stacktracey/versions/1.0.71 — retrieved 2026-10-29T13:19:11.083Z
- https://api.deps.dev/v3/systems/npm/packages/stacktracey/versions/1.0.71:dependencies — retrieved 2026-10-29T13:19:11.139Z