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
- 20
- Versions published
- 12
- First published
- Mar 2026
- Publisher
- mariadias143
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":["@canonical/[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":["@canonical/[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
Scripts12
buildvite build && tsc --emitDeclarationOnly -p tsconfig.build.jsonbuild:allbun run build && bun run build:storybookbuild:storybookstorybook buildcheckbun run check:biome && bun run check:ts && bun run check:webarchitectcheck:biomebiome checkcheck:biome:fixbiome check --writecheck:fixbun run check:biome:fix && bun run check:tscheck:tstsc --noEmitcheck:webarchitectwebarchitect librarystorybookstorybook dev -p 6006 --no-open --host 0.0.0.0testbun run test:vitesttest:vitestvitest run
Dependencies2
@canonical/storybook-config^0.26.0lit^3.3.2