which-native-nodish
Find out if your module or directory is contained in a node-webkit or atom-shell project
which-native-nodish@1.1.3 was published on 2015-08-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 which-native-nodish versions · Permanent reference to 1.1.3
Package specifications
| Version | 1.1.3 |
|---|---|
| License declaration | MIT |
| Published | 2015-08-10T23:07:20.721Z |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 2 |
| Repository forks | 1 |
Install which-native-nodish 1.1.3
npm install which-native-nodish@1.1.3 pnpm add which-native-nodish@1.1.3 yarn add which-native-nodish@1.1.3
Runtime dependencies
- find-parent-dir ^0.3.0
- nodegit-promise ^1.0.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.
- asap@1.0.0 — indirect
- find-parent-dir@0.3.1 — direct
- nodegit-promise@1.0.2 — 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 — project is archived |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 0/10 — Found 1/16 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/which-native-nodish/1.1.3 — retrieved 2026-10-30T04:17:47.735Z
- https://api.deps.dev/v3/systems/npm/packages/which-native-nodish/versions/1.1.3:dependencies — retrieved 2026-10-30T04:17:48.337Z
- https://api.deps.dev/v3/projects/github.com%2Fmaxkorp%2Fwhich-native-nodish — retrieved 2026-10-30T04:17:48.391Z
- https://api.deps.dev/v3/systems/npm/packages/which-native-nodish/versions/1.1.3 — retrieved 2026-10-30T04:17:48.414Z