@cratis/arc.react.mvvm
[](http://nuget.org/packages/Cratis.Arc) [](https://www.npmjs.com/package/@cratis/arc)
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo auto-generated package with SLSA provenance; README/keyword signals are false positives here. | ai |
Versions (showing 18 of 227)
| Version | Deps | Published |
|---|---|---|
| 18.7.1 | 7 / 0 | |
| 18.7.0 | 7 / 0 | |
| 18.6.0 | 7 / 0 | |
| 18.5.0 | 7 / 0 | |
| 18.4.3 | 7 / 0 | |
| 18.4.2 | 7 / 0 | |
| 18.4.1 | 7 / 0 | |
| 18.4.0 | 8 / 0 | |
| 18.1.3 | 8 / 0 | |
| 18.1.2 | 8 / 0 | |
| 18.1.1 | 8 / 0 | |
| 18.1.0 | 8 / 0 | |
| 18.0.5 | 8 / 0 | |
| 18.0.4 | 8 / 0 | |
| 18.0.3 | 8 / 0 | |
| 18.0.2 | 8 / 0 | |
| 18.0.1 | 8 / 0 | |
| 18.0.0 | 8 / 0 |
v18.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.