@sdeverywhere/plugin-check
This package provides a plugin that runs model checks and comparison tests for a given System Dynamics model generated by [SDEverywhere](https://github.com/climateinteractive/SDEverywhere).
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sdeverywhere/runtime | AI (dependencies): Same-monorepo sibling package; not an independent supply-chain risk. | ai | |
| dependencies | unvetted-dep:@sdeverywhere/runtime-async | AI (dependencies): Same-monorepo sibling package; not an independent supply-chain risk. | ai | |
| phantom-deps | phantom-dep:rollup | AI (phantom-deps): rollup referenced in config files only; common pattern for build plugins. | ai | |
| provenance | no-provenance | AI (provenance): Absence of provenance is common (~88% of npm); no other risk signals present. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.3.33 | 11 / 2 | |
| 0.3.32 | 11 / 2 | |
| 0.3.31 | 11 / 2 | |
| 0.3.30 | 11 / 2 | |
| 0.3.29 | 11 / 2 | |
| 0.3.28 | 11 / 2 | |
| 0.3.27 | 11 / 2 | |
| 0.3.26 | 11 / 2 | |
| 0.3.25 | 11 / 2 | |
| 0.3.24 | 11 / 2 | |
| 0.3.23 | 11 / 2 | |
| 0.3.22 | 11 / 2 | |
| 0.3.21 | 11 / 2 | |
| 0.3.20 | 11 / 2 | |
| 0.3.19 | 11 / 2 | |
| 0.3.18 | 11 / 2 | |
| 0.3.17 | 11 / 2 | |
| 0.3.16 | 11 / 2 | |
| 0.3.15 | 11 / 2 | |
| 0.3.14 | 11 / 2 | |
| 0.3.13 | 11 / 2 | |
| 0.3.12 | 11 / 2 | |
| 0.3.11 | 11 / 2 | |
| 0.3.10 | 11 / 2 | |
| 0.3.9 | 11 / 2 | |
| 0.3.8 | 11 / 2 | |
| 0.3.7 | 11 / 2 | |
| 0.3.6 | 11 / 2 |
v0.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.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.