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":["[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
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
Scripts8
buildnpm-run-all -l clean copy:version -p build:esmbuild:esmtsccleanrm -rf distcopy:versionecho "const version = '"$npm_package_version"'; export default version;" > src/version.tslinteslint "src/**/*.ts*" -c ./.eslintrc.cjslint:formatprettier --check "src/**/*.{ts,tsx,md}"testnpm run copy:version && vitest runtest:watchnpm run copy:version && vitest watch
Dependencies12
adm-zip^0.5.10doi-utils^2.0.6jats-tags^1.1.4jats-utils^1.1.4myst-cli-utils^2.0.11myst-common^1.7.5myst-frontmatter^1.7.5node-fetch^3.3.1unist-util-remove4.0.0unist-util-select^4.0.0which^3.0.1xml-js^1.6.11