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,049Established · −30% score
- First published
- Jun 2025
- Publisher
- max-voloshyn
Effective trust discount applied: −30% (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":["@owox/[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":["@owox/[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
Scripts30
buildnest buildbuild:cleanshx rm -rf distbuild:connectorsnpm run build -w @owox/connectors --prefix ../..build:depnpm run build:internal-helpers && npm run build:connectors && npm run build:idp-protocolbuild:idp-protocolnpm run build -w @owox/idp-protocol --prefix ../..build:internal-helpersnpm run build -w @owox/internal-helpers --prefix ../..devnpm run start:devdump:applyts-node commands/apply-dump-command.tsdump:createts-node commands/create-dump-command.tsformatprettier --write "**/*.{ts,json}" --ignore-path ../../.prettierignoreformat:checkprettier --check "**/*.{ts,json}" --ignore-path ../../.prettierignorelinteslint . --config ./eslint.config.mjslint:fixeslint . --fix --config ./eslint.config.mjslint:mdmarkdownlint-cli2 --config ../../.markdownlint-cli2.mjslint:md:fixmarkdownlint-cli2 --config ../../.markdownlint-cli2.mjs --fixmigrations:create-templatets-node commands/create-migration-template-command.tsprebuildnpm run build:clean && npm run build:depprepacknpm run buildprepublishOnlynpm run lintservenpm run start:prodstartnest startstart:debugnest start --debug --watch --env-file ../../.envstart:devnest start --watch --env-file ../../.envstart:prodnode dist/src/maintestjesttest:covjest --coveragetest:debugnode --inspect-brk -r tsconfig-paths/register -r ts-node/register node_modules/.bin/jest --runInBandtest:e2ejest --config ./test/jest-e2e.jsontest:integrationjest --config ./test/jest-integration.jsontest:watchjest --watch
Dependencies45
@aws-sdk/client-athena^3.983.0@aws-sdk/client-redshift-data^3.983.0@aws-sdk/client-s3^3.983.0@databricks/sql^1.12.0@google-cloud/bigquery^8.1.0@google-cloud/pubsub^4.0.7@nestjs/common^11.0.1@nestjs/config^4.0.2@nestjs/core^11.1.2@nestjs/event-emitter^3.0.0@nestjs/platform-express^11.1.3@nestjs/schedule^6.0.0@nestjs/swagger^11.2.0@nestjs/typeorm^11.0.0@owox/connectors0.28.0-next-20260612161252@owox/idp-protocol0.28.0-next-20260612161252@owox/internal-helpers0.28.0-next-20260612161252better-sqlite3^12.2.0class-transformer^0.5.1class-validator^0.14.2compression^1.8.1cross-spawn^7.0.6env-paths^3.0.0googleapis^150.0.1handlebars^4.7.9jsonwebtoken^9.0.0juice^11.0.3luxon^3.6.1mysql2^3.14.1nestjs-cls^6.0.1- …and 15 more.