react-themeable — Greenflagged

Utility for making React components easily themeable

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

markdalgleish

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:coverage/lcov-report/prettify.js	AI (source-diff): This is Google's prettify.js syntax highlighter, auto-generated by babel-istanbul into the coverage/lcov-report directory. It is a standard coverage report artifact, not malicious code.	ai	2026/04/23
source-diff	source-size-tripled	AI (source-diff): Size increase is entirely due to committed coverage/lcov-report artifacts from babel-istanbul, not injected payloads. Actual library source remains minimal.	ai	2026/04/23

Versions (showing 3 of 3)

Version	Deps	Published
1.1.0	1 / 5	2016-05-20
1.0.1	1 / 1	2015-07-07
1.0.0	1 / 1	2015-07-07

v1.1.0

2 findings

HIGH New obfuscated file: coverage/lcov-report/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.