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.
- Versions published
- 24
- First published
- Dec 2025
- Publisher
- yangpei11
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":["@meframe/[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":["@meframe/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
No high-signal static finding in the saved report.
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
No findings stored for this release.
Manifest
Package metadata
Scripts8
buildtsc && pnpm build:cjs && pnpm build:runnerbuild:cjstsc -p tsconfig.cjs.json && node -e "require('node:fs').mkdirSync('dist/cjs', { recursive: true }); require('node:fs').writeFileSync('dist/cjs/package.json', '{\n \"type\": \"commonjs\"\n}\n');"build:runnervite build --config vite.runner.config.tscleanrm -rf distdevnode examples/local/export-to-local.mjstestvitest runtest:watchvitesttype-checktsc --noEmit
Dependencies2
@meframe/core0.5.11puppeteer-core^23.5.0