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
- First published
- May 2026
- Publisher
- itaccounts-ep
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":["@elasticpath/[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":["@elasticpath/[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
Scripts5
buildrimraf ./dist && webpack && chmod 755 ./dist/*clits-node src/cli.tslinteslint --ext .js,.ts .localts-node src/cli.ts loadtestjest --testPathIgnorePatterns='/canonical-model/|/int/' --ci --coverage --collectCoverageFrom='./src/**'
Dependencies10
@moltin/sdk^15.4.1@prismatic-io/spectral^7.2.1bluebird^3.7.2commander^14.0.3dotenv^16.0.1event-stream^4.0.1import-framework-canonical-modelfile:canonical-modelloglevel^1.8.0node-fetch^2.6.6throttled-queue^2.1.4