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
- 11
- Versions published
- 1
- First published
- Oct 2024
- Publisher
- nyayuumi
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":["@react-native-oh-tpl/[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":["@react-native-oh-tpl/[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
Scripts5
buildrm -rf dist && tsclinteslint .prepublishOnlynpm run buildtestjesttest:debugnode --inspect-brk node_modules/.bin/jest --runInBand
Dependencies13
@babel/generator^7.18.7@babel/helper-module-imports7.18.6@babel/types7.19.0css-mediaquery^0.1.2css-to-react-native^3.0.0micromatch^4.0.5postcss^8.4.12postcss-calc^8.2.4postcss-color-functional-notation^4.2.2postcss-css-variables^0.18.0postcss-nested^5.0.6react-is^18.1.0use-sync-external-store^1.1.0