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
- 2,006Mature · −50% score
- First published
- Mar 2018
- Publisher
- saint3347
Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["[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":["[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Large Javascript Payload: 11190394 bytes
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 review · score 3 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Large Javascript Payload | package/dist/shineout.js | 11190394 bytes | 10 |
Manifest
Package metadata
Scripts30
buildNODE_OPTIONS=--openssl-legacy-provider npm-run-all build-*build-cleanrimraf publish .tempbuild-cssnode scripts/build-css.jsbuild-distcross-env NODE_ENV=production webpack --config webpack/config.dist.jsbuild-dist-devcross-env NODE_ENV=development webpack --config webpack/config.dist.dev.jsbuild-es5node scripts/build-es5.jsbuild-esmnode scripts/build-esm.jsbuild-indexnode scripts/src-index.jsbuild-packagenode scripts/build-package.jsbuild-readmecp README.md publish/README.mdbuild-tsnode scripts/build-ts0.jscss-modulecross-env NODE_ENV=development LOCAL_IDENT_NAME=[local]-[hash:base64:5] node dev-server.jscypress:opencross-env NODE_ENV=development cypress opencypress:runcross-env NODE_ENV=development cypress run --browser chromedocs-buildNODE_OPTIONS=--openssl-legacy-provider npm-run-all docs-build-*docs-build-chunkcross-env NODE_ENV=production node scripts/dev-site.jsdocs-build-cleannode scripts/gh-clean.jsdocs-build-featuresnode scripts/build-features.jsdocs-build-htmlnode scripts/build-html.jsdocs-build-jsNODE_OPTIONS=--openssl-legacy-provider cross-env NODE_ENV=production webpack --config webpack/config.doc.js --display-error-details --verbosedocs-rc-buildcross-env LOG_ENV=rc npm-run-all docs-build-*linteslint src/releasenode scripts/publish.jsstartNODE_OPTIONS=--openssl-legacy-provider cross-env NODE_ENV=development LOG_ENV=rc CASE_ENV=test node dev-server.jsstart-sitecross-env NODE_ENV=development node dev-server.jsstylelintstylelint site/**/*.less --fix && stylelint src/**/*.less --fixtestcross-env NODE_ENV=test jest --config jest.config.jstest:covercross-env NODE_ENV=test jest --coveragetest:silentcross-env NODE_ENV=test jest --silenttest:updatejest -u
Dependencies8
@babel/runtime^7.14.6classnames^2.3.2date-fns2.28.0date-fns-tz1.3.6dayjs1.11.3deep-eql^4.0.0immer^4.0.0uuid8.3.2