Automic Vault

npm package intelligence

Install mppx

Nucleus package metadata for mppx, from local Automic Vault package sources.

install

Install with Automic Vault

Automic Vault
sudo av install npm:mppx

Portable and language managers

npm verified ยท 100%
npm install -g mppx

local npm package metadata

Platform notes

  • No package-specific platform notes were present.

overview

Package summary

Homepage

Not present in the local metadata.

Commands and aliases

  • mppx

security posture

No radioisotope coverage found yet

No matching local radioisotope manifest was found for mppx. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No npm postinstall script is recorded in package metadata.
  • Installs with 3 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
mppxcliglobal executable
mppx.srccliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-05-26
manager version0.6.28
manager updated2026-05-24
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/wevm/mppx

install metadata

Package metadata

Package keynpm:mppx
Version0.6.28
Package managernpm
Package manager pagehttps://www.npmjs.com/package/mppx
Repositoryhttps://github.com/wevm/mppx
LicenseMIT
Source archivehttps://registry.npmjs.org/mppx/-/mppx-0.6.28.tgz
Last updated2026-05-24T02:44:27.816Z
Published2026-05-24T02:44:27.816Z
Dependenciesincur, ox, zod
npm postinstallnot defined
Servicenone declared

source trail

Generated from repository data

This page is written by scripts/generate-pkg-pages.py. Deployments refuse to publish if www/pkg/ is stale relative to local package data.

Used sources

  • Nucleus package database
  • cross-ecosystem install command graph
  • package relationship graph
  • package version freshness
  • package-page enrichment