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
- 24
- Versions published
- 12Established · −30% score
- First published
- Jan 2025
- Publisher
- mprinc
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":["@colabo-rima/[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":["@colabo-rima/[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
Scripts21
_buildyarn clean && yarn build:esbuildbuildyarn clean && yarn build:esbuildbuild:esbuildnode esbuild.mjsbuild:rolluprollup -ccleanrm -rf distdeployyarn installecho_nameecho 'Paths: '; echo "LERNA_ROOT_PATH: $LERNA_ROOT_PATH"; echo "LERNA_EXEC_PATH: $LERNA_EXEC_PATH"; echo "LERNA_PACKAGE_NAME: $LERNA_PACKAGE_NAME"install_depsyarn installpackage_buildyarn clean && rm -rf dist && yarn build:esbuildpackage_checktsx $COLABO_FOLDER/scripts/check-package.ts --configPath="$COLABO_FOLDER/scripts/config"package_installyarn installpackage_post_publishtsx $COLABO_FOLDER/scripts/post-publish/single.tspackage_pre_publishtsx $COLABO_FOLDER/scripts/pre-publish/single.tspackage_publishecho "${npm_package_name}:package_publish ----- Publishing the package ----"package_rm_install_lockrm -f yarn.lockpackage_semantic_releasenpx --no-install semantic-release --no-ci --debug -e semantic-release-monorepopackage_update_dependencies_versionstsx $COLABO_FOLDER/scripts/update-dependencies-versions/single.tstestmocha --watch --watch-extensions ts --reporter mocha-clearscreen-reporter -r ts-node/register -r tsconfig-paths/register tests/*.test.tstest_singlemocha --watch --watch-extensions ts --reporter mocha-clearscreen-reporter -r ts-node/register -r tsconfig-paths/registertest_single_no_clearmocha --watch --watch-extensions ts -r ts-node/register -r tsconfig-paths/registerupdate_ver_depstsx scripts/update-dependencies-versions.ts --package $LERNA_PACKAGE_NAME
Dependencies5
@colabo-headless/i-corenpm:@colabo-headless/[email protected]@colabo-knalledge/i-core1.3.2@colabo-knalledge/i-core-services1.5.3@colabo-utils/i-config1.5.1@colabo-utils/i-notifications1.3.2