@murumets-ee/cli Elastic-2.0 51 versions

@murumets-ee/cli

npm

Developer CLI — schema generation, migrations, database tools, SDK generation, and block scaffolding.

51

Versions

Elastic-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

ranx2k

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/dist-Bd6McG-t.mjs	AI (source-diff): Standard tsdown bundle output; content is readable schema/utility code, not obfuscated malware.	ai	2026/05/26
phantom-deps	phantom-dep:jiti	AI (phantom-deps): jiti is a config-loader peer dep used in tsdown/vitest config, not directly imported in source.	ai	2026/05/22
phantom-deps	phantom-dep:picocolors	AI (phantom-deps): picocolors is a transitive/config dep; stable false positive for this package.	ai	2026/05/22
phantom-deps	phantom-dep:drizzle-kit	AI (phantom-deps): drizzle-kit is used as a CLI tool in config, not directly imported.	ai	2026/05/22
phantom-deps	phantom-dep:@clack/prompts	AI (phantom-deps): Likely imported in dist/cli.mjs; phantom-dep heuristic misses bin entrypoints.	ai	2026/05/22
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped org package @murumets-ee/cli; not a typosquat of joi, just a short package name collision.	ai	2026/04/30

Versions (showing 51 of 62)

View all versions

Version	Deps	Published
0.24.1	9 / 5	2026-05-29
0.24.0	9 / 5	2026-05-29
0.23.2	9 / 5	2026-05-24
0.23.1	9 / 5	2026-05-23
0.23.0	9 / 5	2026-05-23
0.22.1	9 / 5	2026-05-22
0.22.0	9 / 5	2026-05-22
0.21.1	9 / 5	2026-05-21
0.21.0	9 / 5	2026-05-21
0.20.0	9 / 5	2026-05-20
0.19.0	9 / 5	2026-05-14
0.18.0	9 / 5	2026-05-14
0.17.1	9 / 5	2026-05-13
0.17.0	9 / 5	2026-05-13
0.16.5	9 / 5	2026-05-13
0.16.4	9 / 5	2026-05-13
0.16.3	9 / 5	2026-05-13
0.16.2	9 / 5	2026-05-13
0.16.1	9 / 5	2026-05-12
0.16.0	9 / 5	2026-05-12
0.15.4	9 / 5	2026-05-12
0.15.3	9 / 5	2026-05-12
0.15.2	9 / 5	2026-05-12
0.15.1	9 / 5	2026-05-12
0.15.0	9 / 5	2026-05-11
0.14.0	8 / 5	2026-05-11
0.13.3	8 / 5	2026-05-10
0.13.2	8 / 5	2026-05-10
0.13.1	8 / 5	2026-05-08
0.13.0	8 / 5	2026-05-08
0.12.0	8 / 5	2026-05-05
0.11.0	8 / 5	2026-04-27
0.10.0	8 / 5	2026-04-26
0.9.0	8 / 5	2026-04-25
0.8.0	8 / 5	2026-04-25
0.7.0	8 / 5	2026-04-24
0.6.1	8 / 5	2026-04-24
0.6.0	8 / 5	2026-04-24
0.5.1	8 / 5	2026-04-22
0.5.0	8 / 5	2026-04-22
0.4.8	4 / 9	2026-04-22
0.4.6	4 / 9	2026-04-21
0.4.5	4 / 9	2026-04-20
0.4.4	4 / 9	2026-04-18
0.4.3	4 / 9	2026-04-18
0.4.2	4 / 9	2026-04-18
0.4.1	4 / 9	2026-04-18
0.4.0	4 / 9	2026-04-18
0.3.0	3 / 8	2026-04-16
0.2.0	3 / 8	2026-04-12
0.1.11	2 / 8	2026-04-10

v0.24.1

1 finding

LOW No provenance attestation provenance

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

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.23.2

1 finding

LOW No provenance attestation provenance

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

v0.23.1

1 finding

LOW No provenance attestation provenance

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

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.22.1

1 finding

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.1

1 finding

LOW No provenance attestation provenance

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

v0.21.0

1 finding

LOW No provenance attestation provenance

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

v0.20.0

1 finding

LOW No provenance attestation provenance

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

v0.19.0

1 finding

LOW No provenance attestation provenance

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

v0.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.1

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.5

1 finding

LOW No provenance attestation provenance

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

v0.16.4

1 finding

LOW No provenance attestation provenance

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

v0.16.3

1 finding

LOW No provenance attestation provenance

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

v0.16.2

1 finding

LOW No provenance attestation provenance

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

v0.16.1

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.4

1 finding

LOW No provenance attestation provenance

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

v0.15.3

1 finding

LOW No provenance attestation provenance

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

v0.15.2

1 finding

LOW No provenance attestation provenance

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

v0.15.1

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

2 findings

HIGH New obfuscated file: dist/dist-Bd6McG-t.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.

v0.13.3

2 findings

HIGH New obfuscated file: dist/dist-Bd6McG-t.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.

v0.13.2

2 findings

HIGH New obfuscated file: dist/dist-Bd6McG-t.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.

v0.13.1

2 findings

HIGH New obfuscated file: dist/dist-Bd6McG-t.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.

v0.13.0

2 findings

HIGH New obfuscated file: dist/dist-Bd6McG-t.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.

v0.12.0

2 findings

HIGH New obfuscated file: dist/dist-Bd6McG-t.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.

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.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.

v0.9.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.

v0.8.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.

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

v0.6.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.

v0.6.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.

v0.5.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.

v0.5.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.

v0.4.8

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.

v0.4.6

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.

v0.4.5

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.

v0.4.4

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.

v0.4.3

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.

v0.4.2

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.

v0.4.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.

v0.4.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.

v0.3.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.

v0.2.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.

v0.1.11

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.