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:esmtsccleanrimraf distcopy:versionecho "const version = '"$npm_package_version"'; export default version;" > src/version.tslinteslint "src/**/!(*.spec).ts" -c .eslintrc.cjs --max-warnings 1lint:formatprettier --check src/*.ts src/**/*.tstestnpm run copy:version && vitest runtest:watchnpm run copy:version && vitest watch
Dependencies19
doi-utils^2.0.6dotenv^16.4.5jats-fetch^1.1.3jats-tags^1.1.3jats-xml^1.1.3js-yaml^4.1.0mathml-to-latex^1.3.0myst-cli-utils^2.0.11myst-common^1.7.5myst-frontmatter^1.7.5myst-spec^0.0.5myst-spec-ext^1.7.5myst-transforms^1.3.28unified^10.0.0unist-builder^3.0.0unist-util-remove^3.1.0unist-util-select^5.1.0vfile^5.0.0xml-js^1.6.11