Package evidence

[email protected]

Install-time lifecycle script: preinstall="node bin/install-demo.js"

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: 143Mature · −50% score
First published: Aug 2018
Publisher: yury-sedinkin

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"}'

Publisheryury-sedinkin

Artifact bytes340,443

Previous version4.10.1

Published2026-05-29T18:15:43.399Z

SHA-25602423a86233e6e28e9f33ef9e886e7d075dd5e3bf3567507c8d50afa1672af26

Why flagged

What the scanner saw

Install-time lifecycle script: preinstall="node bin/install-demo.js"

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

Availability ledger

available

review

19d agoLast checked

reviewRisk

1Score

4.11.0Version

Status history (1 event)

new → available19d ago · risk review · score 1 · 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	Install-time lifecycle script	package.json	preinstall="node bin/install-demo.js"	5
low	Obfuscation Density	package/src/parser/generated/FHIRPathParser.js	high encoded/escaped-token density	0

Manifest

Package metadata

Scripts11

buildcd browser-build && webpack && rimraf fhirpath.zip && bestzip fhirpath.zip LICENSE.md fhirpath.min.js fhirpath.r5.min.js fhirpath.r4.min.js fhirpath.stu3.min.js fhirpath.dstu2.min.js && rimraf LICENSE.md
build:demonpm run build && cd demo && npm run build
compare-performancenode --max-old-space-size=4096 --initial-old-space-size=4096 --max-semi-space-size=128 --min-semi-space-size=128 ./test/benchmark.js
generateParsercd src/parser; rimraf ./generated/*; java -Xmx500M -cp "../../antlr-4.9.3-complete.jar:$CLASSPATH" org.antlr.v4.Tool -o generated -Dlanguage=JavaScript FHIRPath.g4; node ../../scripts/fix-parser-imports.js
linteslint src/parser/index.js src/*.js converter/
preinstallnode bin/install-demo.js
testnpm run lint && npm run test:tsd && npm run test:unit && npm run test:e2e && echo "For tests specific to IE 11, open browser-build/test/index.html in IE 11, and confirm that the tests on that page pass."
test:e2enpm run build:demo && cypress run
test:tsdtsd
test:unitnode --use_strict node_modules/jest/bin/jest.js && TZ=America/New_York node --use_strict node_modules/jest/bin/jest.js && TZ=Europe/Paris node --use_strict node_modules/jest/bin/jest.js
test:unit:debugecho 'open chrome chrome://inspect/' && node --inspect node_modules/jest/bin/jest.js --runInBand

Dependencies7

@lhncbc/ucum-lhc^5.0.0
@loxjs/url-join^1.0.2
antlr4~4.9.3
commander^14.0.3
date-fns^1.30.1
decimal.js^10.6.0
js-yaml^4.1.1