publish 0.2.1

npm auto publishing of your modules

publish@0.2.1 was published on 2012-07-24. Its manifest declares 4 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 publish versions · Permanent reference to 0.2.1 · Latest release

Package specifications

Version	0.2.1
License declaration	MIT
Published	2012-07-24T14:55:47.621Z
Node.js requirement	Not declared
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	65
Repository stars	13
Repository forks	7

Install publish 0.2.1

npm install publish@0.2.1
pnpm add publish@0.2.1
yarn add publish@0.2.1

Runtime dependencies

npm 1.1.x
nopt 1.0.x
npmlog 0.0.2
semver 1.0.x

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.

abbrev@1.1.1 — indirect
ansi@0.1.2 — indirect
ansi-regex@5.0.1 — indirect
aproba@2.1.0 — indirect
are-we-there-yet@4.0.2 — indirect
color-support@1.1.3 — indirect
console-control-strings@1.1.0 — indirect
emoji-regex@8.0.0 — indirect
gauge@5.0.2 — indirect
has-unicode@2.0.1 — indirect
inherits@1.0.2 — indirect
inherits@2.0.4 — indirect
is-fullwidth-code-point@3.0.0 — indirect
nopt@1.0.10 — direct
npm@1.1.71 — direct
npm>1.1.71>abbrev@1.0.3 — indirect
npm>1.1.71>ansi@0.1.2 — indirect
npm>1.1.71>archy@0.0.2 — indirect
npm>1.1.71>block-stream@0.0.6 — indirect
npm>1.1.71>chownr@0.0.1 — indirect
npm>1.1.71>fstream@0.1.21 — indirect
npm>1.1.71>fstream-npm@0.1.3 — indirect
npm>1.1.71>fstream-npm>fstream-ignore@0.0.5 — indirect
npm>1.1.71>glob@3.1.14 — indirect
npm>1.1.71>graceful-fs@1.1.14 — indirect
npm>1.1.71>inherits@1.0.0 — indirect
npm>1.1.71>ini@1.0.5 — indirect
npm>1.1.71>init-package-json@0.0.6 — indirect
npm>1.1.71>init-package-json>promzard@0.2.0 — indirect
npm>1.1.71>lockfile@0.2.1 — indirect
npm>1.1.71>lru-cache@2.0.4 — indirect
npm>1.1.71>minimatch@0.2.9 — indirect
npm>1.1.71>minimatch>sigmund@1.0.0 — indirect
npm>1.1.71>mkdirp@0.3.4 — indirect
npm>1.1.71>node-gyp@0.8.2 — indirect
npm>1.1.71>nopt@2.0.0 — indirect
npm>1.1.71>npm-registry-client@0.2.11 — indirect
npm>1.1.71>npm-registry-client>couch-login@0.1.15 — indirect
npm>1.1.71>npmconf@0.0.16 — indirect
npm>1.1.71>npmconf>config-chain@1.1.3 — indirect
npm>1.1.71>npmconf>config-chain>proto-list@1.2.2 — indirect
npm>1.1.71>npmlog@0.0.2 — indirect
npm>1.1.71>once@1.1.1 — indirect
npm>1.1.71>opener@1.3.0 — indirect
npm>1.1.71>osenv@0.0.3 — indirect
npm>1.1.71>read@1.0.4 — indirect
npm>1.1.71>read-installed@0.0.4 — indirect
npm>1.1.71>read-package-json@0.1.12 — indirect
npm>1.1.71>read>mute-stream@0.0.3 — indirect
npm>1.1.71>request@2.9.203 — indirect
npm>1.1.71>retry@0.6.0 — indirect
npm>1.1.71>rimraf@2.1.1 — indirect
npm>1.1.71>semver@1.1.2 — indirect
npm>1.1.71>slide@1.1.3 — indirect
npm>1.1.71>tar@0.1.14 — indirect
npm>1.1.71>uid-number@0.0.3 — indirect
npm>1.1.71>which@1.0.5 — indirect
npmlog@0.0.2 — direct
npmlog@7.0.1 — indirect
semver@1.0.14 — direct
set-blocking@2.0.0 — indirect
signal-exit@4.1.0 — indirect
string-width@4.2.3 — indirect
strip-ansi@6.0.1 — indirect
wide-align@1.1.5 — 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	1/10 — Found 4/24 approved changesets -- score normalized to 1
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
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/publish/0.2.1 — retrieved 2026-10-30T07:48:51.345Z
https://api.deps.dev/v3/projects/github.com%2Fcmanzana%2Fnode-publish — retrieved 2026-10-30T06:29:42.685Z
https://api.deps.dev/v3/systems/npm/packages/publish/versions/0.2.1 — retrieved 2026-10-30T07:48:51.842Z
https://api.deps.dev/v3/systems/npm/packages/publish/versions/0.2.1:dependencies — retrieved 2026-10-30T07:48:51.876Z