chromatic 18.13.4
PkgFire would install this release with a warning.·Checked 13 hours ago·Published 28 October 2026
Why
-
warnSuspicious behaviour
Detects suspicious autostart persistence mechanisms
-
warnSuspicious behaviour
Detects advanced API call obfuscation using introspection and reflection techniques
-
warnSuspicious behaviour
Detects steganography decode followed by code execution
-
warnSuspicious behaviour
Detects unicode homoglyphs and uncommon characters used for obfuscation
-
warnSuspicious behaviour
Difference between manifest and package.json found: scripts: typescript:check: Manifest("tsc --project ./tsconfig.json --noEmit"), package.json("None") postpack: Manifest("clean-package restore"), package.json("None") chromatic-staging: Manifest("CHROMATIC_INDEX_URL=https://www.staging-chromatic.com ./dist/bin.cjs"), package.json("None") release: Manifest("./scripts/release.mjs"), package.json("None") publish-action: Manifest("./scripts/publishAction.mjs"), package.json("None") chromatic-prebuilt: Manifest("./dist/bin.cjs --storybook-build-dir="storybook-static""), package.json("None") dev: Manifest("tsdown --watch"), package.json("None") trace: Manifest("./dist/bin.cjs trace"), package.json("None") build-storybook: Manifest("cross-env FORCE_COLOR=3 TERM=xterm-256color storybook build --stats-json"), package.json("None") fixture: Manifest("node e2e/prepare.mjs"), package.json("None") lint: Manifest("yarn lint:js bin-src node-src ./isChromatic.js ./isChromatic.mjs"), package.json("None") release-next: Manifest("./scripts/releaseNext.mjs"), package.json("None") chromatic: Manifest("./dist/bin.cjs"), package.json("None") trim-stats: Manifest("./dist/bin.cjs trim-stats-file"), package.json("None") prepack: Manifest("clean-package"), package.json("None") chromatic-verbose: Manifest("cross-env LOG_LEVEL=verbose ./dist/bin.cjs"), package.json("None") lint:package: Manifest("sort-package-json"), package.json("None") prepare: Manifest("yarn run build"), package.json("None") clean:sourcemaps: Manifest("rm -f dist/*.map && rm -f action/*.map"), package.json("None") build: Manifest("clean-package && tsdown && clean-package restore"), package.json("None") lint:js: Manifest("cross-env NODE_ENV=production eslint --cache --cache-location=.cache/eslint --report-unused-disable-directives"), package.json("None") test: Manifest("vitest run --coverage"), package.json("None") storybook: Manifest("cross-env FORCE_COLOR=3 TERM=xterm-256color storybook dev -p 9009"), package.json("None")
-
warnSuspicious behaviour
Possible credential in the published package: generic-api-key
-
warnRelease cooldown
Published 3 days ago, inside the 7-day cooldown. Most malicious releases are pulled within hours of publication, so a version this new has not yet had time to be caught.
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Verified against the registry's key
- Build provenance
- Attested · source commit ↗
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.