project-name 0.2.3

Get the name of a project, from package.json, git config, or basename of the current working directory.

project-name@0.2.3 was published on 2015-11-28. Its manifest declares 3 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 project-name versions · Permanent reference to 0.2.3 · Latest release

Package specifications

Version	0.2.3
License declaration	MIT
Published	2015-11-28T03:55:00.871Z
Node.js requirement	>=0.10.0
Type declarations	Not declared
Runtime dependency count	3
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	20
Repository stars	12
Repository forks	5

Install project-name 0.2.3

npm install project-name@0.2.3
pnpm add project-name@0.2.3
yarn add project-name@0.2.3

Runtime dependencies

find-pkg ^0.1.0
git-repo-name ^0.5.1
lazy-cache ^0.2.4

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.

cwd@0.9.1 — indirect
expand-tilde@1.2.2 — indirect
file-name@0.1.0 — indirect
find-file-up@0.1.3 — indirect
find-pkg@0.1.2 — direct
fs-exists-sync@0.1.0 — indirect
git-repo-name@0.5.1 — direct
global-modules@0.2.3 — indirect
global-prefix@0.1.5 — indirect
homedir-polyfill@1.0.3 — indirect
ini@1.3.8 — indirect
is-windows@0.2.0 — indirect
isexe@2.0.0 — indirect
lazy-cache@0.2.7 — direct
os-homedir@1.0.2 — indirect
parse-git-config@0.2.0 — indirect
parse-passwd@1.0.0 — indirect
remote-origin-url@0.4.0 — indirect
resolve-dir@0.1.1 — indirect
which@1.3.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/28 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
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	0/10 — security policy file not detected
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/project-name/0.2.3 — retrieved 2026-10-29T22:42:02.084Z
https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fproject-name — retrieved 2026-10-29T21:38:52.164Z
https://api.deps.dev/v3/systems/npm/packages/project-name/versions/0.2.3 — retrieved 2026-10-29T22:42:02.606Z
https://api.deps.dev/v3/systems/npm/packages/project-name/versions/0.2.3:dependencies — retrieved 2026-10-29T22:42:02.626Z