← Home

@sogni-ai/sogni-creative-agent-skill

npm Repository Homepage

Sogni Creative Agent Skill: agent skill and CLI for Sogni AI image and video generation.

21
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

lytvynenkosvkrunkosaurusmarkledford

Keywords

sogniaiagentimage-generationvideo-generationmusic-generationaudio-generationopenclawhermes-agentmanusclaudeclaude-code

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): env-spread is in a dev/check script that spawns a subprocess with inherited env — standard and intentional pattern for this package. ai

Versions (showing 21 of 21)

Version Deps Published
3.5.1 4 / 6
3.5.0 4 / 6
3.4.0 4 / 6
3.3.5 4 / 6
3.3.4 4 / 6
3.3.3 4 / 6
3.3.2 4 / 6
3.3.1 4 / 6
3.3.0 4 / 6
3.2.0 4 / 6
3.1.1 4 / 6
3.1.0 4 / 6
2.3.0 4 / 0
2.2.0 4 / 0
2.1.3 4 / 0
2.1.2 4 / 0
2.1.1 4 / 0
2.1.0 4 / 0
2.0.2 5 / 0
2.0.1 5 / 0
2.0.0 5 / 0

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

1 finding
LOW No provenance attestation provenance

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

v3.4.0

1 finding
LOW No provenance attestation provenance

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

v3.3.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: markledford → krunkosaurus (on 2026-05-28, known maintainer) provenance

This version was published by a different npm account (krunkosaurus) than the most recent previously approved version (markledford) on 2026-05-28, but krunkosaurus is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.3.4

1 finding
LOW No provenance attestation provenance

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

v3.3.3

1 finding
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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: krunkosaurus → markledford (on 2026-05-21, known maintainer) provenance

This version was published by a different npm account (markledford) than the most recent previously approved version (krunkosaurus) on 2026-05-21, but markledford is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.2.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: krunkosaurus → markledford (on 2026-05-21, known maintainer) provenance

This version was published by a different npm account (markledford) than the most recent previously approved version (krunkosaurus) on 2026-05-21, but markledford is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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.

v2.3.0

2 findings
HIGH env-spread: scripts/check-creative-agent-runtime.mjs:36 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Sogni-AI/sogni-creative-agent-skill/blob/951e7c53a4862ec766c995bda1cedfcdfc969dc1/scripts/check-creative-agent-runtime.mjs#L36 34 | const beforeSync = readFileSync(generatedPath, 'utf8'); 35 | const syncResult = run(process.execPath, [syncScript], { > 36 | env: { 37 | ...process.env, 38 | SOGNI_CREATIVE_AGENT_SKILL_DIR: repoRoot,

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.

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.3

2 findings
HIGH env-spread: scripts/check-creative-agent-runtime.mjs:36 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Sogni-AI/sogni-creative-agent-skill/blob/19f338a2c25a97c32780a57d9b558d2be23ea5bb/scripts/check-creative-agent-runtime.mjs#L36 34 | const beforeSync = readFileSync(generatedPath, 'utf8'); 35 | const syncResult = run(process.execPath, [syncScript], { > 36 | env: { 37 | ...process.env, 38 | SOGNI_CREATIVE_AGENT_SKILL_DIR: repoRoot,

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.

v2.1.2

2 findings
HIGH env-spread: scripts/check-creative-agent-runtime.mjs:36 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Sogni-AI/sogni-creative-agent-skill/blob/95c2b880e08b7fa422357803180ba6e79256e211/scripts/check-creative-agent-runtime.mjs#L36 34 | const beforeSync = readFileSync(generatedPath, 'utf8'); 35 | const syncResult = run(process.execPath, [syncScript], { > 36 | env: { 37 | ...process.env, 38 | SOGNI_CREATIVE_AGENT_SKILL_DIR: repoRoot,

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.

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

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

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

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

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