schemastery No license 51 versions

schemastery

npm Repository Homepage

51

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

shigma

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file-transition:lib/browser.js	AI (source-diff): esbuild-bundled browser output, not malicious obfuscation.	ai	2026/07/21
source-diff	obfuscated-file:lib/index.mjs	AI (source-diff): Bundled/minified ESM output, not true obfuscation; stable across releases.	ai	2026/07/21
source-diff	obfuscated-file:lib/browser.js	AI (source-diff): Minified esbuild browser bundle (module entrypoint), not obfuscation; no malicious behavior.	ai	2026/07/21
dependencies	unvetted-dep:tikloot	AI (dependencies): New dep with no malicious behavior evidence; trusted publisher track record.	ai	2026/07/21
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	2026/04/26
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	2026/04/26

Versions (showing 51 of 51)

Version	Deps	Published
3.18.0	2 / 3	2026-03-09
3.17.2	1 / 2	2025-11-11
3.17.1	1 / 2	2025-10-02
3.17.0	1 / 2	2025-08-26
3.16.1	1 / 2	2025-03-03
3.16.0	1 / 2	2025-02-09
3.15.0	1 / 2	2025-01-26
3.14.7	1 / 2	2024-11-24
3.14.6	1 / 0	2024-04-24
3.14.5	1 / 0	2024-03-25
3.14.4	1 / 0	2024-03-17
3.14.3	1 / 0	2024-01-01
3.14.2	1 / 0	2023-12-12
3.14.1	1 / 0	2023-11-05
3.14.0	1 / 0	2023-10-18
3.13.1	1 / 0	2023-10-02
3.13.0	1 / 0	2023-09-17
3.12.0	1 / 0	2023-09-10
3.11.1	1 / 0	2023-07-20
3.11.0	1 / 0	2023-07-18
3.10.2	1 / 0	2023-07-18
3.10.1	1 / 0	2023-06-25
3.10.0	1 / 0	2023-06-19
3.9.0	1 / 0	2023-05-26
3.8.1	1 / 0	2023-05-16
3.8.0	1 / 0	2023-05-14
3.7.5	1 / 0	2023-05-05
3.7.4	1 / 0	2023-05-05
3.7.3	1 / 0	2023-05-01
3.7.2	1 / 0	2023-03-04
3.7.1	1 / 0	2023-02-20
3.7.0	1 / 0	2023-01-29
3.6.1	1 / 0	2022-12-07
3.6.0	1 / 0	2022-12-06
3.5.4	1 / 0	2022-08-30
3.5.3	1 / 0	2022-08-20
3.5.2	1 / 0	2022-08-19
3.5.1	1 / 0	2022-07-31
3.5.0	1 / 0	2022-07-26
3.4.3	1 / 10	2022-05-21
3.4.2	1 / 9	2022-05-21
3.4.1	0 / 9	2022-05-21
3.4.0	1 / 2	2022-05-16
3.3.3	1 / 10	2022-04-25
3.3.2	1 / 10	2022-04-21
3.3.1	1 / 10	2022-04-19
3.3.0	1 / 7	2022-04-19
3.2.0	0 / 7	2022-04-10
3.1.1	0 / 7	2022-03-13
3.1.0	0 / 7	2022-03-03
3.0.0	0 / 7	2022-02-24

v3.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.14.7

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.14.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.14.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.14.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.14.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.14.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.14.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.13.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.0

2 findings

HIGH New obfuscated file: lib/index.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.3

2 findings

HIGH New obfuscated file: lib/browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.2

2 findings

HIGH New obfuscated file: lib/browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.1

2 findings

HIGH New obfuscated file: lib/browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.0

2 findings

HIGH New obfuscated file: lib/browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.3

2 findings

HIGH New obfuscated file: lib/browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

2 findings

HIGH Modified file became obfuscated: lib/browser.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.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.