Package evidence
@photostructure/[email protected]
Install-time lifecycle script: install="node scripts/install.cjs"
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
- 31Mature · −50% score
- First published
- Nov 2024
- Publisher
- GitHub ActionsTrusted automation · −70% score
Effective trust discount applied: −70% (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":["@photostructure/[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":["@photostructure/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Install-time lifecycle script: install="node scripts/install.cjs"
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 1 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Install-time lifecycle script | package.json | install="node scripts/install.cjs" | 5 |
Manifest
Package metadata
Scripts37
// fmt:cppon ubuntu: `sudo apt install clang-format`. Note that windows emits `invalid format` with this || true approach, but it works and is better than introducing Yet Another Script Script (like scripts/clang-format.mjs).// precommitshould be manually run by developers before they run `git commit`// testsupport `npm t name_of_file` (and don't fail due to missing coverage)buildrun-s build:native build:distbuild:disttsup && node scripts/post-build.mjsbuild:linux-glibcbash scripts/prebuild-linux-glibc.shbuild:nativetsx scripts/prebuildify-wrapper.tscheck:memorytsx scripts/check-memory.tscleanrun-p clean:*clean:distdel-cli coverage dist docs "*.tsbuildinfo"clean:gyp-cachedel-cli --force build %USERPROFILE%/.node-gyp ~/.node-gypclean:nativenode-gyp cleandocstypedocfmtrun-p fmt:*fmt:cppclang-format --style=LLVM -i src/*.cpp src/*/*.cpp src/*/*.h || echo "problem with clang-format"fmt:jsprettier --write "**/*.{cjs,mjs,js}"fmt:jsonprettier --write "**/*.json"fmt:mdprettier --write "**/*.md"fmt:pkgnpm pkg fixfmt:tsprettier --write "**/*.{cts,mts,ts}"fmt:ymlprettier --write "**/*.{yaml,yml}"installnode scripts/install.cjsinstall:pinactgo install github.com/suzuki-shunsuke/pinact/v3/cmd/pinact@latestlintrun-s lint:*lint:eslinteslintlint:nativetsx scripts/clang-tidy.tslint:tsctsc --noEmitnode-gyp-rebuildnode-gyp rebuildprecommitnpx --yes tsx scripts/precommit.tsprepare-releasenpm run build:dist- …and 7 more.
Dependencies2
node-addon-api^8.7.0node-gyp-build^4.8.4