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
- 3
- First published
- May 2026
- Publisher
- robertyangfundamental
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":["@mog-sdk/[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":["@mog-sdk/[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
buildtsup && tsc -p tsconfig.build.json && api-extractor run --local --verbose && find dist -maxdepth 2 -not -path 'dist/.rollup/*' \( -name '*.d.ts' -o -name '*.d.ts.map' \) -delete && cp dist/.rollup/index.d.ts dist/index.d.ts && node -e "const fs=require('node:fs');const p='dist/index.d.ts';const ref='/// <reference lib=\"esnext.disposable\" />\n';const s=fs.readFileSync(p,'utf8');if(!s.startsWith(ref))fs.writeFileSync(p,ref+s);" && rm -rf dist/.rollupcheck-typestsc -b .testjesttypechecktsc -b .
Dependencies1
@mog-sdk/contracts0.6.0