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
- 205Mature · −50% score
- First published
- Oct 2022
- Publisher
- jonmiller_hs
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":["@hubspot/[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":["@hubspot/[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
Scripts16
buildtsc -noEmit && yarn run copy-html && yarn build-types && node scripts/build.mjs && npm run publintbuild-typestsc --project tsconfig.types.jsonbuild:watchnodemon --exec 'yarn build'cleantsc --build --cleancopy-htmlcopyfiles -u 1 'src/html/**' 'dist'devnodemon --no-stdin --exec 'yarn start'dev-inspectnodemon --exec 'yarn start-inspect'es-watchesbuild --outfile=dist-esbuild/runWhenDeveloping.cjs --bundle --watch --platform=node --external:fsevents --external:vite --external:react-refresh runWhenDeveloping.tspackagenpm run build && npm packpreparenpm run buildpublintpublint --level warning --prodrunBuildnode dist/run.jsstarttsx runWhenDeveloping.tsstart-inspectnode --import tsx --inspect runWhenDeveloping.tstestPORT=30042 NODE_ENV=test vitest runtest:watchPORT=30042 NODE_ENV=test vitest watch
Dependencies50
@babel/code-frame^7.24.7@babel/parser^7.25.3@babel/traverse^7.25.3@babel/types^7.25.2@hubspot/cms-components^1.2.36@hubspot/local-dev-lib4.0.2@inquirer/select^2.0.0@originjs/vite-plugin-commonjs^1.0.3@radix-ui/react-dialog^1.1.2@radix-ui/react-separator^1.1.0@radix-ui/react-slot^1.1.0@radix-ui/react-toggle^1.1.3@radix-ui/react-tooltip^1.1.4@sentry/node^6.2.0@storybook/addon-actions^8.6.15@storybook/addon-essentials^8.6.15@storybook/addon-interactions^8.6.15@storybook/addon-links^8.6.15@storybook/builder-vite^8.6.15@storybook/react^8.6.15@storybook/react-vite^8.6.15@storybook/test^8.6.15@vitejs/plugin-react^4.2.1ansi-to-html0.7.xbabel-plugin-macros^3.1.0babel-plugin-styled-components^2.1.4chalk^5.3.0class-variance-authority^0.7.0cli-progress^3.12.0clsx^2.1.1- …and 20 more.