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
- 517
- Versions published
- 6
- First published
- May 2026
- Publisher
- rw3iss
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":["@pageloop/[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":["@pageloop/[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
Scripts4
buildtsc -p tsconfig.jsoncleanrm -rf dist *.tsbuildinfotestvitest runtypechecktsc -p tsconfig.json --noEmit
Dependencies14
@pageloop/external0.6.1@pageloop/git-adapter0.6.1@pageloop/loader0.6.1@pageloop/mail0.6.1@pageloop/payments-stripe0.6.1@pageloop/persistence0.6.1@pageloop/server0.6.1@pageloop/shared0.6.1@pageloop/vanilla0.6.1better-sqlite3^11.7.0cheerio^1.0.0commander^13.0.0nanoid^5.0.9postgres^3.4.5