findup-sync 0.1.3
Find the first file matching a given pattern in the current directory or the nearest ancestor directory.
findup-sync@0.1.3 was published on 2014-03-14. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.6.0.
All findup-sync versions · Permanent reference to 0.1.3 · Latest release
Package specifications
| Version | 0.1.3 |
|---|---|
| License declaration | Not declared |
| Published | 2014-03-14T14:30:47.366Z |
| Node.js requirement | >= 0.6.0 |
| 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 | lib/findup-sync |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 99 |
| Repository forks | 27 |
Install findup-sync 0.1.3
npm install findup-sync@0.1.3 pnpm add findup-sync@0.1.3 yarn add findup-sync@0.1.3
Runtime dependencies
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.
- glob@3.2.11 — direct
- inherits@2.0.4 — indirect
- lodash@2.4.2 — direct
- lru-cache@2.7.3 — indirect
- minimatch@0.3.0 — indirect
- sigmund@1.0.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.
| Code-Review | 0/10 — Found 2/29 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| 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 |
| Security-Policy | 10/10 — security policy 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/findup-sync/0.1.3 — retrieved 2026-10-29T09:11:58.394Z
- https://api.deps.dev/v3/projects/github.com%2Fgulpjs%2Ffindup-sync — retrieved 2026-10-29T09:11:58.643Z
- https://api.deps.dev/v3/systems/npm/packages/findup-sync/versions/0.1.3 — retrieved 2026-10-29T09:11:58.956Z
- https://api.deps.dev/v3/systems/npm/packages/findup-sync/versions/0.1.3:dependencies — retrieved 2026-10-29T09:11:58.984Z