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
- 1
- First published
- May 2026
- Publisher
- kyle-ssg
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":["@flagsmith/[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":["@flagsmith/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Remote Payload: matched "curl "
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 15 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Payload | package/package.json | matched "curl " | 12 |
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Payload | package/package.json | matched "curl " | 12 |
| low | Credential file access | package/.github/workflows/release-please.yml | matched "GITHUB_TOKEN" | 3 |
Manifest
Package metadata
Scripts13
buildtsc -b tsconfig.cjs.json tsconfig.esm.json && echo '{"type": "commonjs"}'> build/cjs/package.jsondeploynpm i && npm run build && npm publishdeploy:betanpm i && npm run build && npm publish --tag betagenerate-engine-typesnpm run generate-evaluation-result-types && npm run generate-evaluation-context-typesgenerate-evaluation-context-typescurl -o evaluation-context.json https://raw.githubusercontent.com/Flagsmith/flagsmith/main/sdk/evaluation-context.json && npx json2ts -i evaluation-context.json -o flagsmith-engine/evaluation/evaluationContext/evaluationContext.types.ts && rm evaluation-context.jsongenerate-evaluation-result-typescurl -o evaluation-result.json https://raw.githubusercontent.com/Flagsmith/flagsmith/main/sdk/evaluation-result.json && npx json2ts -i evaluation-result.json -o flagsmith-engine/evaluation/evaluationResult/evaluationResult.types.ts && rm evaluation-result.jsonlintprettier --write .prebuildrm -rf ./buildpreparehusky installtestvitest --coverage --runtest:debugvitest --inspect-brk --no-file-parallelism --coveragetest:esm-buildnpm run build && ESM_BUILD=true vitest --config vitest.config.esm.ts --runtest:watchvitest
Dependencies4
jsonpath-plus^10.4.0pino^10semver^7.3.7undici-types^6.19.8