connected-react-router No license 21 versions

connected-react-router

npm Repository Homepage

21

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

supasate

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file-transition:umd/ConnectedReactRouter.js	AI (source-diff): Webpack UMD build artifact, not obfuscation; minified dist is expected for this file.	ai	2026/07/21
semgrep	semgrep:new-function-constructor	AI (semgrep): The new Function() usage is in a webpack-generated UMD bundle wrapper — standard UMD boilerplate, not dynamic code execution of user input. Stable false positive for this package.	ai	2026/04/26
dependencies	unvetted-dep:lodash.isequalwith	AI (dependencies): lodash.isequalwith is a well-known lodash modular package; its use here for deep equality comparison is legitimate and expected.	ai	2026/04/26
dependencies	unvetted-dep:redux-seamless-immutable	AI (dependencies): redux-seamless-immutable is an intentional runtime dependency supporting optional immutable state integration; its inclusion is consistent with the library's documented feature set across all versions.	ai	2026/04/26
phantom-deps	phantom-dep:redux-seamless-immutable	AI (phantom-deps): Declared but not directly imported because it's an optional integration dependency; this pattern is stable for this package across versions.	ai	2026/04/26
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance; no provenance is expected for this established project and is not a security concern.	ai	2026/04/26

Versions (showing 21 of 21)

Version	Deps	Published
6.9.3	4 / 38	2022-07-11
6.9.2	4 / 38	2021-11-28
6.9.1	4 / 38	2021-02-22
6.9.0	3 / 39	2021-02-22
6.8.0	1 / 38	2020-03-15
6.7.0	1 / 38	2020-02-09
6.6.1	3 / 35	2019-11-25
6.6.0	3 / 35	2019-11-17
6.5.2	3 / 35	2019-07-13
6.5.1	3 / 35	2019-07-13
6.5.0	3 / 35	2019-07-02
6.4.0	3 / 35	2019-04-14
6.3.2	2 / 36	2019-03-10
6.3.1	2 / 35	2019-02-12
6.3.0	2 / 35	2019-02-10
6.2.2	2 / 34	2019-01-20
6.2.1	2 / 33	2019-01-13
6.2.0	2 / 33	2019-01-12
6.1.0	2 / 33	2018-12-27
6.0.0	2 / 33	2018-12-09
4.5.0	3 / 33	2018-09-23

v6.9.2

2 findings

HIGH Modified file became obfuscated: umd/ConnectedReactRouter.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

INFO No provenance attestation provenance

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

v6.9.1

2 findings

HIGH Modified file became obfuscated: umd/ConnectedReactRouter.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

INFO No provenance attestation provenance

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

v6.9.0

2 findings

HIGH Modified file became obfuscated: umd/ConnectedReactRouter.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

INFO No provenance attestation provenance

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

v6.8.0

2 findings

HIGH Modified file became obfuscated: umd/ConnectedReactRouter.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

INFO No provenance attestation provenance

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

v6.7.0

2 findings

HIGH Modified file became obfuscated: umd/ConnectedReactRouter.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

INFO No provenance attestation provenance

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

v6.6.1

2 findings

HIGH Modified file became obfuscated: umd/ConnectedReactRouter.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

INFO No provenance attestation provenance

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

v6.6.0

2 findings

HIGH Modified file became obfuscated: umd/ConnectedReactRouter.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

INFO No provenance attestation provenance

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

v6.5.2

1 finding

INFO No provenance attestation provenance

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

v6.5.1

1 finding

INFO No provenance attestation provenance

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

v6.5.0

1 finding

INFO No provenance attestation provenance

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

v6.4.0

1 finding

INFO No provenance attestation provenance

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

v6.3.2

1 finding

INFO No provenance attestation provenance

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

v6.3.1

1 finding

INFO No provenance attestation provenance

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

v6.3.0

1 finding

INFO No provenance attestation provenance

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

v6.2.2

1 finding

INFO No provenance attestation provenance

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

v6.2.1

1 finding

INFO No provenance attestation provenance

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

v6.2.0

1 finding

INFO No provenance attestation provenance

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

v6.1.0

1 finding

INFO No provenance attestation provenance

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

v6.0.0

1 finding

INFO No provenance attestation provenance

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