PkgRadar

Package evidence

@sassoftware/[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
63Mature · −50% score
First published
Mar 2024
Publisher
devakumaraswamy

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":["@sassoftware/[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":["@sassoftware/[email protected]"],"fail_on":"review"}'
Publisherdevakumaraswamy
Artifact bytes158,350
Previous version0.18.1
Published2024-05-04T20:05:10.887Z
SHA-25668ec922005e6b41d19ba2a5656c57e0d417aae1550b34a0a09a6e809d4684192

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
0.19.0Version
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

Scripts11
  • azureaidotenvx run -f .env.azureai -- npm test
  • buildrimraf dist && microbundle --name viyaAssistantjs
  • debugcd example && cross-env NODE_TLS_REJECT_UNAUTHORIZED=0 node --inspect-brk cli
  • debugadotenvx run -f .env.azureai -- npm run debug
  • debugodotenvx run -f .env.openai -- npm run debug
  • jsdocrimraf docs && jsdoc -c jsdoc.json
  • linteslint . --ext .js --fix
  • openaidotenvx run -f .env.openai -- npm test
  • pubnpm publish --tag dev --access public
  • startcross-env NODE_TLS_REJECT_UNAUTHORIZED=0 node --no-warnings cli
  • testcd example && node cli.js
Dependencies4
  • @azure/openai^1.0.0-beta.12
  • @azure/openai-assistants^1.0.0-beta.5
  • @sassoftware/restafedit^2.4.8
  • openai^4.38.3