Package evidence
[email protected]
Remote Dependency Spec: devDependencies.json-schema-test-suite="https://github.com/json-schema-org/JSON-Schema-Test-Suite.git"
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
- 467
- Versions published
- 61Mature · −50% score
- First published
- May 2025
- Publisher
- germanbisurgi
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 promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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"}'Why flagged
What the scanner saw
Remote Dependency Spec: devDependencies.json-schema-test-suite="https://github.com/json-schema-org/JSON-Schema-Test-Suite.git"
1 remote tarball(s) were followed statically.
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 review · score 4 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Remote Dependency Spec | package.json | devDependencies.json-schema-test-suite="https://github.com/json-schema-org/JSON-Schema-Test-Suite.git" | 8 |
Remote payloads
Followed remote artifacts
| Source | URL | Risk | Score | Summary |
|---|---|---|---|---|
| devDependencies.json-schema-test-suite | https://github.com/json-schema-org/JSON-Schema-Test-Suite.git | error | 0 | invalid gzip header |
Manifest
Package metadata
Scripts19
buildvite build --config ./vite.config.prod.jsdevvite --config ./vite.config.dev.jse2eyarn e2e:clean && start-server-and-test serve http://localhost:8181 'codeceptjs run-workers 10 -c tests/e2e/codecept.conf.cjs'e2e:*yarn e2e && yarn e2e:b3 && yarn e2e:b4 && yarn e2e:b5e2e:b3yarn e2e:clean && THEME='bootstrap3' start-server-and-test serve http://localhost:8181 'codeceptjs run-workers 10 -c tests/e2e/codecept.conf.cjs'e2e:b4yarn e2e:clean && THEME='bootstrap4' start-server-and-test serve http://localhost:8181 'codeceptjs run-workers 10 -c tests/e2e/codecept.conf.cjs'e2e:b5yarn e2e:clean && THEME='bootstrap5' start-server-and-test serve http://localhost:8181 'codeceptjs run-workers 10 -c tests/e2e/codecept.conf.cjs'e2e:cleanrimraf ./tests/e2e/output/*e2e:grepyarn e2e:clean && SHOW=true THEME='bootstrap5' start-server-and-test serve http://localhost:8181 'codeceptjs run -c tests/e2e/codecept.conf.cjs --steps --debug --grep @issue-44'e2e:grep:headlessyarn e2e:clean && start-server-and-test serve http://localhost:8181 'codeceptjs run-workers 10 -c tests/e2e/codecept.conf.cjs --grep @issue-44'linteslint -c ./.eslintrc.json ./src ./testslint:fixeslint --fix -c ./.eslintrc.json ./src ./testspostversiongit push && git push --tagsprebuildvite build --config ./vite.config.pages.jspreservevite build --config ./vite.config.dev.jsreleasenpm publish --access publicservevite preview --config ./vite.config.dev.jstest:fullyarn e2e:clean && yarn e2e && yarn unitunityarn build && jest --config=./tests/unit/jest.config.cjs