@springtree/eva-sdk-redux-store-builder
Provide the means to create an EVA focused Redux store
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:redux-logic | AI (dependencies): redux-logic is a known Redux middleware library; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived org package published via GitHub Actions; provenance absence is consistent across all 371 versions. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Proprietary SpringTree SDK; UNLICENSED is intentional for this package family. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 9 / 0 | |
| 9.0.15 | 9 / 0 | |
| 9.0.14 | 9 / 0 | |
| 9.0.13 | 9 / 0 | |
| 9.0.12 | 9 / 0 | |
| 9.0.11 | 9 / 0 | |
| 9.0.10 | 9 / 0 | |
| 9.0.9 | 9 / 0 | |
| 9.0.8 | 9 / 0 | |
| 9.0.7 | 9 / 0 | |
| 9.0.6 | 9 / 0 | |
| 9.0.5 | 9 / 0 | |
| 9.0.4 | 9 / 0 | |
| 9.0.3 | 9 / 0 | |
| 9.0.2 | 9 / 0 | |
| 9.0.1 | 9 / 0 | |
| 9.0.0 | 9 / 0 |
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.