mobx-react-lite
Lightweight React bindings for MobX based on React 16.8+ and Hooks
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package migrated to mobxjs/mobx monorepo build system, explaining the changed publish environment and missing gitHead. Not a security concern for this well-established package. | ai | |
| provenance | no-provenance | AI (provenance): Established package by original MobX author; lack of Sigstore attestation is a process gap, not a security risk for this publisher. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 4.1.1 | 1 / 2 | |
| 4.1.0 | 1 / 2 | |
| 4.0.7 | 1 / 2 | |
| 4.0.6 | 1 / 2 | |
| 4.0.5 | 1 / 2 | |
| 4.0.4 | 1 / 2 | |
| 4.0.3 | 1 / 2 | |
| 4.0.2 | 1 / 2 | |
| 4.0.1 | 0 / 3 | |
| 3.4.3 | 0 / 2 | |
| 3.4.2 | 0 / 2 | |
| 3.4.1 | 0 / 2 | |
| 3.4.0 | 0 / 2 | |
| 3.3.0 | 0 / 2 | |
| 3.2.3 | 0 / 2 | |
| 3.2.2 | 0 / 2 | |
| 3.2.1 | 0 / 2 | |
| 3.2.0 | 0 / 2 | |
| 3.1.7 | 0 / 2 | |
| 3.1.6 | 0 / 2 | |
| 3.1.5 | 0 / 2 | |
| 3.1.4 | 0 / 2 | |
| 3.1.3 | 0 / 2 | |
| 3.1.2 | 0 / 2 | |
| 3.1.1 | 0 / 2 | |
| 3.1.0 | 0 / 37 | |
| 3.0.1 | 0 / 36 | |
| 3.0.0 | 0 / 34 | |
| 2.2.2 | 0 / 34 | |
| 2.2.1 | 0 / 34 | |
| 2.2.0 | 0 / 34 | |
| 2.1.0 | 0 / 34 | |
| 2.0.7 | 0 / 34 | |
| 2.0.6 | 0 / 34 | |
| 2.0.5 | 0 / 31 | |
| 2.0.4 | 0 / 31 | |
| 2.0.3 | 0 / 31 | |
| 2.0.2 | 0 / 31 | |
| 2.0.1 | 0 / 31 | |
| 2.0.0 | 0 / 31 | |
| 1.5.2 | 0 / 34 | |
| 1.5.1 | 0 / 34 | |
| 1.5.0 | 0 / 34 | |
| 1.4.2 | 0 / 34 | |
| 1.4.1 | 0 / 32 | |
| 1.4.0 | 0 / 32 | |
| 1.3.2 | 0 / 32 | |
| 1.3.1 | 0 / 32 | |
| 1.3.0 | 0 / 32 | |
| 1.2.0 | 0 / 30 | |
| 1.1.1 | 0 / 30 |
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mweststrate.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mweststrate.
v3.1.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mweststrate.
v3.1.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mweststrate.
v3.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mweststrate.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.