← Home

@kosmojs/dev

TODO: Add package description

18
Versions
MIT
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

sleewoo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:typescript AI (phantom-deps): typescript is a declared dependency used as a build-time tool/type-checker, not directly imported in source. ai
semgrep semgrep:env-spread AI (semgrep): env-spread is used to pass process.env to a Node Worker thread — standard pattern, not exfiltration. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped @kosmojs package; Levenshtein match to ajv is coincidental, not impersonation. ai

Versions (showing 18 of 18)

Version Deps Published
0.1.8 16 / 0
0.1.7 16 / 0
0.1.6 16 / 0
0.1.2 1 / 14
0.1.1 1 / 14
0.0.26 11 / 2
0.0.23 14 / 2
0.0.21 13 / 3
0.0.11 16 / 20
0.0.10 16 / 20
0.0.9 16 / 23
0.0.8 16 / 23
0.0.7 16 / 22
0.0.6 17 / 20
0.0.3 18 / 4
0.0.2 18 / 4
0.0.1 18 / 4
0.0.0 16 / 4

v0.1.8

1 finding
LOW No provenance attestation provenance

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

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

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

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

2 findings
HIGH env-spread: pkg/index.js:1499 semgrep

Spreading entire process.env into an object — may capture all secrets 1497 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 1498 | workerData, > 1499 | env: { 1500 | ...process.env, 1501 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:1499 semgrep

Spreading entire process.env into an object — may capture all secrets 1497 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 1498 | workerData, > 1499 | env: { 1500 | ...process.env, 1501 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:913 semgrep

Spreading entire process.env into an object — may capture all secrets 911 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 912 | workerData, > 913 | env: { 914 | ...process.env, 915 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:913 semgrep

Spreading entire process.env into an object — may capture all secrets 911 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 912 | workerData, > 913 | env: { 914 | ...process.env, 915 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:884 semgrep

Spreading entire process.env into an object — may capture all secrets 882 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 883 | workerData, > 884 | env: { 885 | ...process.env, 886 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:820 semgrep

Spreading entire process.env into an object — may capture all secrets 818 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 819 | workerData, > 820 | env: { 821 | ...process.env, 822 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:817 semgrep

Spreading entire process.env into an object — may capture all secrets 815 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 816 | workerData, > 817 | env: { 818 | ...process.env, 819 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:816 semgrep

Spreading entire process.env into an object — may capture all secrets 814 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 815 | workerData, > 816 | env: { 817 | ...process.env, 818 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:816 semgrep

Spreading entire process.env into an object — may capture all secrets 814 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 815 | workerData, > 816 | env: { 817 | ...process.env, 818 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:816 semgrep

Spreading entire process.env into an object — may capture all secrets 814 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 815 | workerData, > 816 | env: { 817 | ...process.env, 818 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:816 semgrep

Spreading entire process.env into an object — may capture all secrets 814 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 815 | workerData, > 816 | env: { 817 | ...process.env, 818 | FORCE_COLOR: "1"

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

2 findings
HIGH env-spread: pkg/index.js:816 semgrep

Spreading entire process.env into an object — may capture all secrets 814 | return new Worker(resolve5(import.meta.dirname, "base-plugin/worker.js"), { 815 | workerData, > 816 | env: { 817 | ...process.env, 818 | FORCE_COLOR: "1"

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.