schemastery
4
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
shigma
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is used for controlled callback deserialization within schemastery's own schema objects, wrapped in try/catch. This is a stable, legitimate pattern for this schema library, not a malware indicator. | ai | |
| dependencies | unvetted-dep:cosmokit | AI (dependencies): cosmokit is authored by the same publisher (shigma) and is a core utility in the Koishi/schemastery ecosystem; not a suspicious dependency. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.18.0 | 2 / 3 | |
| 3.17.2 | 1 / 2 | |
| 3.17.1 | 1 / 2 | |
| 3.17.0 | 1 / 2 |
v3.18.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.