PkgRadar

Package evidence

@plasmicpkgs/[email protected]

no findings

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
216Mature · −50% score
First published
Mar 2023
Publisher
plasmicapp

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 monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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":["@plasmicpkgs/[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":["@plasmicpkgs/[email protected]"],"fail_on":"review"}'
Publisherplasmicapp
Artifact bytes387,731
Previous version1.0.256
Published2026-06-16T22:31:43.770Z
SHA-256010caf3634f224785fb15f22efe4ebe61e6a8cc55a5da623511e5da7c89bb5be

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

low
Last checked
lowRisk
0Score
1.0.257Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts5
  • analyzesize-limit --why
  • buildrollup -c rollup.config.mjs && yarn tsc --emitDeclarationOnly --declaration src/index.tsx --incremental --tsBuildInfoFile ./dist/.tsbuildinfo --skipLibCheck --jsx react --lib dom,esnext --esModuleInterop --strict --outDir ./dist/ && rsync -r --include='*/' --include='*.d.ts' --exclude='*' ./dist/ ./skinny/ && rm skinny/index.d.ts
  • prepublishOnlynpm run build
  • sizesize-limit
  • testTEST_CWD=`pwd` yarn --cwd=../.. test --passWithNoTests
Dependencies7
  • @ctrl/tinycolor^3.6.1
  • @plasmicpkgs/luxon-parser^3.4.4
  • classnames^2.3.2
  • csv-writer-browser^1.0.0
  • dayjs^1.11.10
  • fast-stringify^2.0.0
  • lodash^4.17.21