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
- 14
- First published
- May 2026
- Publisher
- louismazel
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":["@maz-ui/[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":["@maz-ui/[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
Scripts9
buildunbuildcodegennx builddevunbuild --stublintcross-env NODE_ENV=production eslint .lint:fixpnpm lint --fixtest:unitvitest runtest:unit:coveragevitest run --coveragetest:unit:watchvitest watchtypechecktsc --build
Dependencies11
consola^3.4.2postcss-html^1.8.1postcss-scss^4.0.9stylelint-config-html^1.1.0stylelint-config-recess-order^7.7.0stylelint-config-recommended-vue^1.6.1stylelint-config-standard^40.0.0stylelint-config-standard-scss^17.0.0stylelint-order^8.1.1stylelint-plugin-tailwindcss^2.0.5stylelint-use-logical-spec^5.0.1