Package evidence

[email protected]

Credential file access: matched "AWS_ACCESS_KEY"

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: 1,371Niche · −30% score
Versions published: 175Mature · −50% score
First published: May 2024
Publisher: hassanzohdy

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

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarball Add 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":["[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":["[email protected]"],"fail_on":"review"}'

Publisherhassanzohdy

Artifact bytes163,067

Previous version4.1.12

Published2026-06-03T11:14:00.972Z

SHA-256e7fff82ffb6631a1e93eec9ba9c18a114484e6aefb838ae959969cee798802ee

Why flagged

What the scanner saw

Credential file access: matched "AWS_ACCESS_KEY"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review

21h agoLast checked

reviewRisk

5Score

4.1.13Version

Status history (1 event)

new → available21h ago · risk review · score 5 · status changed

Evidence

Static findings

2 static · 0 from release diff · showing high-signal first.

No high-signal findings — see all findings below.

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
low	Credential file access	package/templates/warlock/src/config/storage.ts	matched "AWS_ACCESS_KEY"	5
low	Install-time lifecycle script	package.json	postinstall="agent-kit init && agent-kit sync \|\| echo skills-sync-skipped"	5

Manifest

Package metadata

Scripts26

buildtsc && warlock build
devwarlock dev
formatnpx prettier --write ./src/**/*.{js,jsx,ts,tsx,css,md,json} --config ./.prettierrc.json
genwarlock generate.module
gen.cwarlock.generate.controller
gen.mwarlock.generate.model
gen.mdwarlock generate.model
gen.migwarlock generate.migration
gen.rwarlock generate.repository
gen.rswarlock generate.resource
gen.swarlock.generate.service
gen.vwarlock generate.validation
jwtwarlock jwt.generate
lffind . -type d ( -name 'node_modules' -o -name '.git' ) -prune -o -type f -exec dos2unix {} ;
lintnpx eslint --fix ./src --max-warnings=0
migratewarlock migrate
migrate.freshwarlock migrate --fresh
migrate.listwarlock migrate --list
postinstallagent-kit init && agent-kit sync || echo skills-sync-skipped
preparehuskier-init && husky install
seedwarlock seed
serveyarn build && nohup warlock start > /dev/null 2>&1
skills:syncagent-kit sync
skills:watchagent-kit watch
startwarlock start
tscnpx tsc --noEmit

Dependencies12

@mongez/localization^3.4.6
@mongez/reinforcements^3.1.16
@mongez/supportive-is^2.1.3
@warlock.js/auth4.0.119
@warlock.js/cache4.0.119
@warlock.js/cascade4.0.119
@warlock.js/core4.0.119
@warlock.js/fs4.0.119
@warlock.js/logger4.0.119
@warlock.js/scheduler4.0.119
@warlock.js/seal4.0.119
dayjs^1.11.19