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
- 76
- First published
- Mar 2026
- Publisher
- dylanbrown
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":["@actalk/[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":["@actalk/[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
buildtscdevtsc --watchprebuildpnpm run prepare:workspace-coreprepare:workspace-corepnpm --filter @actalk/inkos-core buildpretestpnpm run buildpretypecheckpnpm run prepare:workspace-coretestvitest run --passWithNoTeststypechecktsc --noEmit
Dependencies10
@actalk/inkos-core1.5.0-rc.1-canary.46.2@actalk/inkos-studio1.5.0-rc.1-canary.46.2commander^13.0.0dotenv^16.4.0epub-gen-memory^1.0.10ink^7.0.0ink-text-input^6.0.0marked^15.0.12marked-terminal^7.3.0react^19.2.4