@memlab/core
memlab core libraries
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @memlab/core is a scoped Meta/Facebook package unrelated to cors; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:ansi | AI (phantom-deps): Declared runtime dep used transitively or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:xvfb | AI (phantom-deps): xvfb is used for headless browser support; may be conditionally imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:util.promisify | AI (phantom-deps): util.promisify polyfill may be used indirectly; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 10 / 7 | |
| 2.0.2 | 10 / 7 | |
| 2.0.1 | 10 / 7 | |
| 2.0.0 | 10 / 7 |
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsPackage name '@memlab/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.