safeps 2.2.7
Work with processes safely and easily with Node.js
safeps@2.2.7 was published on 2013-08-29. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.4.
All safeps versions · Permanent reference to 2.2.7 · Latest release
Package specifications
| Version | 2.2.7 |
|---|---|
| License declaration | Not declared |
| Published | 2013-08-29T05:20:57.682Z |
| Node.js requirement | >=0.4 |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| 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 | ./out/lib/safeps.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 17 |
| Repository forks | 5 |
Install safeps 2.2.7
npm install safeps@2.2.7 pnpm add safeps@2.2.7 yarn add safeps@2.2.7
Runtime dependencies
- typechecker ~2.0.1
- safefs ~3.0.1
- taskgroup ~3.2.0
- extract-opts ~2.2.0
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.
- ambi@2.1.6 — indirect
- extendonclass@1.0.1 — indirect
- extract-opts@2.2.0 — direct
- graceful-fs@2.0.3 — indirect
- safefs@3.0.6 — direct
- taskgroup@3.2.4 — direct
- taskgroup@3.3.9 — indirect
- typechecker@2.0.8 — 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.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Security-Policy | 10/10 — security policy file detected |
| Maintained | 6/10 — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Code-Review | 0/10 — Found 0/6 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 |
| 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 | 7/10 — SAST tool is not run on all commits -- score normalized to 7 |
Evidence and freshness
- https://registry.npmjs.org/safeps/2.2.7 — retrieved 2026-10-29T23:00:38.661Z
- https://api.deps.dev/v3/projects/github.com%2Fbevry%2Fsafeps — retrieved 2026-10-29T21:12:55.187Z
- https://api.deps.dev/v3/systems/npm/packages/safeps/versions/2.2.7 — retrieved 2026-10-29T23:00:39.152Z
- https://api.deps.dev/v3/systems/npm/packages/safeps/versions/2.2.7:dependencies — retrieved 2026-10-29T23:00:39.185Z