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":["@dr.pogodin/[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":["@dr.pogodin/[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
Scripts11
buildrimraf build && npm run build:types-code && npm run build:types-scss && npm run build:common && npm run build:modulebuild:commonrimraf build/common && babel src -x .ts,.tsx --out-dir build/common --source-mapsbuild:modulerimraf build/module && babel src -x .ts,.tsx --out-dir build/module --source-maps --config-file ./babel-module.config.jsbuild:types-coderimraf build/types-code && tsc --project tsconfig.types.jsonbuild:types-scssrimraf build/types-scss && typed-scss-modules .jestnpm run jest:types && npm run jest:logicjest:logicjest --config jest/config.json --no-cachejest:typeststychelinteslinttestnpm run lint && npm run typecheck && npm run jesttypechecktsc --project __tests__/tsconfig.json
Dependencies1
@babel/runtime^7.28.6