@sdeverywhere/compile
The core Vensim to C compiler for the SDEverywhere tool suite.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): fflate is a well-established compression library; replacement of xlsx with fflate is a benign dependency swap. | ai | |
| dependencies | unvetted-dep:xlsx | AI (dependencies): xlsx from cdn.sheetjs.com is the documented SheetJS distribution; not a suspicious URL dep. | ai | |
| dependencies | unvetted-dep:@sdeverywhere/parse | AI (dependencies): First-party sibling package from the same SDEverywhere monorepo; low risk. | ai | |
| npm-metadata | url-dep:xlsx | AI (npm-metadata): SheetJS distributes via cdn.sheetjs.com as their official channel; stable pattern for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.31 | 6 / 0 | |
| 0.7.30 | 6 / 0 | |
| 0.7.29 | 6 / 0 | |
| 0.7.28 | 6 / 0 | |
| 0.7.27 | 6 / 0 | |
| 0.7.26 | 6 / 0 | |
| 0.7.24 | 7 / 0 |
v0.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.