← Home

preact-transition-group

npm Repository Homepage

transition-group ui component for preact

4
Versions
MIT
License
No
Install Scripts
Missing
Provenance

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

developitharmonyjdecroocklukeedmarvinhagemeisterprateekbhpreactjsreznordsolarliner

Keywords

preactpreact-componentpreact-transition-group

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/preact-transition-group.modern.js AI (source-diff): Standard microbundle minified output for a Preact component library. Code is readable minified JS, not obfuscated. Stable pattern for this package's build toolchain. ai
source-diff obfuscated-file:dist/preact-transition-group.mjs AI (source-diff): Standard microbundle minified ESM output. Code logic is clearly a transition-group component, not obfuscated malware. Stable pattern for this package. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are known Preact org members (jdecroock, lukeed, marvinhagemeister, preactjs, etc.). Legitimate transfer to the preactjs organization by the original author developit. ai

Versions (showing 4 of 4)

Version Deps Published
2.0.0 0 / 11
1.1.1 0 / 39
1.1.0 0 / 39
1.0.0 0 / 39

v2.0.0

3 findings
HIGH New obfuscated file: dist/preact-transition-group.modern.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.

HIGH New obfuscated file: dist/preact-transition-group.mjs 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.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

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.