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
- 1,047Mature · −50% score
- First published
- May 2023
- Publisher
- wanchongyang
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
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":["@zat-design/[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":["@zat-design/[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
Scripts31
analyzeANALYZE=1 dumi buildbuildfather build && mv dist/index.min.css dist/index.esm.css && mv dist/less.min.css dist/less.esm.cssbuild-distfather build --format umdbuild-esfather build --format esmbuild-libfather build --format cjscode-standards:checknode ./scripts/code-standards-check.mjscommit-msg:formatnode ./scripts/format-commit-msg.mjsdocscross-env NODE_OPTIONS="--openssl-legacy-provider" dumi builddocs:deploygh-pages -d docs-distgit:pull:dev_4git pull --tags --no-rebase origin dev_4lintnpm run lint:js && npm run lint:style && npm run lint:prettierlint-stagedlint-stagedlint-staged:jseslint --ext .js,.jsx,.ts,.tsx --ignore-pattern '**/__tests__/**' --ignore-pattern '**/*.test.*' --ignore-pattern '**/*.spec.*'lint:fixeslint --fix --cache --ext .js,.jsx,.ts,.tsx --format=pretty ./srclint:jseslint --cache --ext .js,.jsx,.ts,.tsx --format=pretty ./srclint:prettierprettier --check "**/*" --end-of-line autolint:reporteslint --ext .jsx,.js src -f checkstyle -o report_zacc_eslint_js.xml & exit 0; stylelint --custom-formatter node_modules/stylelint-checkstyle-formatter src/**/*.{css,scss,less} > report_zacc_stylelint_css.xml & exit 0lint:stylestylelint --fix "src/**/*.less"postpublishgit clean -fdprecommitlint-stagedpreparehusky && patch-packageprettierprettier --write '**/*.{js,jsx,tsx,ts,less,md,json}'releaseyarn build && npm publishrelease:betayarn build && npm publish --tag=betastartcross-env NODE_OPTIONS="--openssl-legacy-provider" dumi devtestumi-testtest:all-versionsnpm run test:react18 && npm run test:react19test:coverageumi-test --coveragetest:react18REACT_VERSION=18 npm run testtest:react19npm run test- …and 1 more.
Dependencies12
@dnd-kit/core^6.0.8@dnd-kit/sortable^7.0.2@dnd-kit/utilities^3.2.1@zat-design/utils^4.0.0big.js^6.2.1classnames^2.3.1dayjs^1.11.13idb-keyval^6.2.2lodash^4.17.21react-intersection-observer^9.13.0react-resizable^3.0.5react-svg^15.1.7