@jsdevtools/npm-publish 4.0.0

Fast, easy publishing to NPM

@jsdevtools/npm-publish@4.0.0 was published on 2025-09-14. Its manifest declares 5 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.

All @jsdevtools/npm-publish versions · Permanent reference to 4.0.0 · View npm registry JSON · Latest release

Package specifications

Version	4.0.0
License declaration	MIT
Published	2025-09-14T20:32:14.623Z
Node.js requirement	>=20
Type declarations	Bundled declarations
Runtime dependency count	5
Peer requirement count	0
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	134.60 KiB
Published file count	80
Package type	module
ES module entry	Not declared
Default entry	Not declared
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	15
Repository stars	666
Repository forks	82

Install @jsdevtools/npm-publish 4.0.0

npm install @jsdevtools/npm-publish@4.0.0
pnpm add @jsdevtools/npm-publish@4.0.0
yarn add @jsdevtools/npm-publish@4.0.0

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.

@isaacs/fs-minipass@4.0.1 — indirect
@types/semver@7.8.0 — direct
array-back@6.2.3 — indirect
chownr@3.0.0 — indirect
command-line-args@6.0.1 — direct
find-replace@5.0.2 — indirect
lodash.camelcase@4.3.0 — indirect
minipass@7.1.3 — indirect
minizlib@3.1.0 — indirect
mkdirp@3.0.1 — indirect
semver@7.7.2 — direct
tar@7.4.3 — direct
typical@7.3.0 — indirect
validate-npm-package-name@6.0.2 — direct
yallist@5.0.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.

Dangerous-Workflow	10/10 — no dangerous workflow patterns detected
Binary-Artifacts	10/10 — no binaries found in the repo
Code-Review	0/10 — Found 1/19 approved changesets -- score normalized to 0
Maintained	0/10 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Token-Permissions	0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies	6/10 — dependency not pinned by hash detected -- score normalized to 6
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
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

Readable npm registry JSON — retrieved 2026-11-09T12:02:25.313Z
https://api.deps.dev/v3/projects/github.com%2FJS-DevTools%2Fnpm-publish — retrieved 2026-11-09T11:29:01.797Z
https://api.deps.dev/v3/systems/npm/packages/%40jsdevtools%2Fnpm-publish/versions/4.0.0 — retrieved 2026-11-09T12:02:25.390Z
https://api.deps.dev/v3/systems/npm/packages/%40jsdevtools%2Fnpm-publish/versions/4.0.0:dependencies — retrieved 2026-11-09T12:02:25.481Z