reselect
Selectors for Redux.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/reselect.browser.mjs | AI (source-diff): tsup-bundled minified dist output, not obfuscation; stable build artifact. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New dist bundles/sourcemaps from tsup build migration. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Known Redux team handoff; publisher stable 960d on npm. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from maintainer to GitHub Actions CI/CD with SLSA provenance; expected for reduxjs org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature stable package; infrequent releases are normal for reselect. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() is used legitimately in a Proxy trap for autotrack memoization — standard JS Proxy pattern, not obfuscation. Stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 0 / 28 | |
| 5.1.1 | 0 / 28 | |
| 5.1.0 | 0 / 28 | |
| 5.0.1 | 0 / 28 | |
| 5.0.0 | 0 / 28 | |
| 4.0.0 | 0 / 26 |
v5.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (eskimojo) than the most recent previously approved version (ellbee) on 2024-01-05, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v5.0.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (acemarke) than the most recent previously approved version (ellbee) on 2023-12-04. It has since remained available on npm for 960 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (acemarke) than the most recent previously approved version (ellbee) on 2023-12-04. It has since remained available on npm for 960 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.