@memlab/cli
command line interface for memlab
4
Versions
MIT
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
npm-memlabjacksonglmeta-memlab
Keywords
climemlabmemoryleakheapsnapshot
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established Meta OSS tool; inactivity gap plausible for a mature project; no code changes vs prior approved version. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): False positive: @memlab/cli is a scoped Meta OSS package, not a typosquat of joi. | ai | |
| phantom-deps | phantom-dep:ansi | AI (phantom-deps): ansi is a declared dep used indirectly via config; stable false positive for this package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Documented preinstall step for memlab CLI setup; stable pattern across versions of this Meta OSS package. | ai | |
| phantom-deps | phantom-dep:babar | AI (phantom-deps): babar is a declared dep for CLI chart rendering; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:util.promisify | AI (phantom-deps): util.promisify declared dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:xvfb | AI (phantom-deps): xvfb used for headless browser testing; referenced in config, stable false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 15 / 8 | |
| 2.0.2 | 15 / 8 | |
| 2.0.1 | 15 / 8 | |
| 2.0.0 | 15 / 8 |
v2.0.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.