is-valid-app 0.1.2
Wrapper around is-valid-instance and is-registered for validating `base` plugins. Returns true if `app` is a valid instance of base and a plugin is not registered yet.
is-valid-app@0.1.2 was published on 2016-06-21. 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.10.0.
All is-valid-app versions · Permanent reference to 0.1.2 · Latest release
Package specifications
| Version | 0.1.2 |
|---|---|
| License declaration | MIT |
| Published | 2016-06-21T17:46:40.250Z |
| Node.js requirement | >=0.10.0 |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 18 |
| Repository stars | 3 |
| Repository forks | 1 |
Install is-valid-app 0.1.2
npm install is-valid-app@0.1.2 pnpm add is-valid-app@0.1.2 yarn add is-valid-app@0.1.2
Runtime dependencies
- debug ^2.2.0
- is-registered ^0.1.5
- is-valid-instance ^0.1.0
- lazy-cache ^2.0.1
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.
- debug@2.6.9 — direct
- define-property@0.2.5 — indirect
- function-bind@1.1.2 — indirect
- hasown@2.0.4 — indirect
- is-accessor-descriptor@1.0.2 — indirect
- is-buffer@1.1.6 — indirect
- is-data-descriptor@1.0.1 — indirect
- is-descriptor@0.1.8 — indirect
- is-registered@0.1.5 — direct
- is-valid-instance@0.1.0 — direct
- isarray@1.0.0 — indirect
- isobject@2.1.0 — indirect
- kind-of@3.2.2 — indirect
- lazy-cache@2.0.2 — direct
- ms@2.0.0 — indirect
- pascalcase@0.1.1 — indirect
- set-getter@0.1.1 — indirect
- to-object-path@0.3.0 — 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.
| Code-Review | 0/10 — Found 0/16 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| 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 | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/is-valid-app/0.1.2 — retrieved 2026-10-29T21:37:14.624Z
- https://api.deps.dev/v3/projects/github.com%2Fnode-base%2Fis-valid-app — retrieved 2026-10-29T19:47:00.872Z
- https://api.deps.dev/v3/systems/npm/packages/is-valid-app/versions/0.1.2 — retrieved 2026-10-29T21:37:15.159Z
- https://api.deps.dev/v3/systems/npm/packages/is-valid-app/versions/0.1.2:dependencies — retrieved 2026-10-29T21:37:15.287Z