Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Weekly downloads
- 497
- Versions published
- 13
- First published
- May 2026
- Publisher
- rblez_
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["@memlink/[email protected]"],"fail_on":"review"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["@memlink/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Large Javascript Payload: 2573925 bytes
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Large Javascript Payload | package/dist/cli/index.js | 2573925 bytes | 0 |
| low | Large Javascript Payload | package/dist/server/index.js | 2234064 bytes | 0 |
Manifest
Package metadata
Scripts18
buildbun build src/cli/index.ts --outdir dist/cli --target node && bun build src/server/index.ts --outdir dist/server --target nodebuild:binariesbun run build:binary:linux-amd64 && bun run build:binary:linux-arm64 && bun run build:binary:darwin-amd64 && bun run build:binary:darwin-arm64build:binary:darwin-amd64bun build --compile --minify --target=bun-darwin-x64 --outfile=dist/binaries/memlink-darwin-amd64 src/cli/index.tsbuild:binary:darwin-arm64bun build --compile --minify --target=bun-darwin-arm64 --outfile=dist/binaries/memlink-darwin-arm64 src/cli/index.tsbuild:binary:linux-amd64bun build --compile --minify --target=bun-linux-x64 --outfile=dist/binaries/memlink-linux-amd64 src/cli/index.tsbuild:binary:linux-arm64bun build --compile --minify --target=bun-linux-arm64 --outfile=dist/binaries/memlink-linux-arm64 src/cli/index.tsbuild:binary:windows-amd64bun build --compile --minify --target=bun-windows-x64 --outfile=dist/binaries/memlink-windows-amd64.exe src/cli/index.tsclibun src/cli/index.tsdev:clibun src/cli/index.tsdev:serverbun --watch src/server/index.tsformatprettier --write "src/**/*.ts" "tests/**/*.ts"format:checkprettier --check "src/**/*.ts" "tests/**/*.ts"linteslint src --ext .tslint:fixeslint src --ext .ts --fixprepublishOnlynpm run buildstartnode dist/server/index.jstestbun testtest:watchbun test --watch
Dependencies8
@modelcontextprotocol/sdk^1.29.0chalk^5.6.2commander^14.0.3express^5.2.1express-rate-limit^8.5.2nanoid^5.1.11table^6.9.0zod^4.4.3