JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 21
  • Score
    100M100P100Q68852F
  • License MIT

Inspect and apply install-time cooldown (min-release-age / exclude-newer) for npm and uv.

Package Exports

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@hikae/pmsec) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    @hikae/pmsec (Node)

    Cross-platform CLI that inspects and applies install-time cooldown settings (npm min-release-age, pnpm minimum-release-age, yarn npmMinimalAgeGate, bun minimumReleaseAge, cargo minimum-release-age, mise minimum_release_age, uv exclude-newer) so freshly-published, possibly-malicious packages can't land in your machine within hours of upload.

    Install

    npx @hikae/pmsec check --min 7
    npx @hikae/pmsec set 7
    npx @hikae/pmsec unset
    uvx pmsec check --min 7
    uvx pmsec set 7
    uvx pmsec unset

    If your environment already enforces cooldown (or routes through a proxy registry), bootstrap pmsec by overriding just for that call:

    npx --registry=https://registry.npmjs.org/ --min-release-age=0 @hikae/pmsec check
    uvx --index https://pypi.org/simple --exclude-newer-package pmsec=2099-01-01 pmsec check

    Zero runtime dependencies, ESM, requires Node 20+.

    Commands

    Command Description
    pmsec check [--min N] Read each tool's config; exit 1 if any tool is below N days or unset.
    pmsec set <DAYS> Write DAYS-day cooldown to every selected tool. Always proceeds; if the runtime is too old to honor the key, prints a line under the success line.
    pmsec unset Remove only the cooldown key from each config (other keys preserved).

    Options: --tool npm,pnpm,yarn,bun,cargo,mise,uv, --json.

    When the target file is owned by another user (typical: ~/.npmrc left root-owned by an old sudo npm config set), pmsec auto-runs sudo chown $(id -u):$(id -g) <path> and retries the write. You'll be prompted for your password once; subsequent runs need no escalation.

    See the project README for the full table of keys, units, paths, and environment overrides.

    License

    MIT