flagged-respawn 0.1.2
A tool for respawning node binaries when special flags are present.
flagged-respawn@0.1.2 was published on 2014-09-04. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.8.0.
All flagged-respawn versions · Permanent reference to 0.1.2 · Latest release
Package specifications
| Version | 0.1.2 |
|---|---|
| License declaration | Not declared |
| Published | 2014-09-04T17:17:38.651Z |
| Node.js requirement | >= 0.8.0 |
| Type declarations | Not declared |
| Runtime dependency count | 0 |
| 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 | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 21 |
| Repository forks | 5 |
Install flagged-respawn 0.1.2
npm install flagged-respawn@0.1.2 pnpm add flagged-respawn@0.1.2 yarn add flagged-respawn@0.1.2
Runtime dependencies
- None declared
Peer requirements
- None declared
Optional dependencies
- None declared
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 |
|---|---|
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| 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/29 approved changesets -- score normalized to 0 |
| Pinned-Dependencies | 5/10 — dependency not pinned by hash detected -- score normalized to 5 |
| 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 | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/flagged-respawn/0.1.2 — retrieved 2026-11-01T05:45:17.236Z
- https://api.deps.dev/v3/projects/github.com%2Fgulpjs%2Fflagged-respawn — retrieved 2026-10-31T11:12:17.020Z (stale snapshot; refresh pending)