@sogni-ai/sogni-creative-agent-skill
Sogni Creative Agent Skill: agent skill and CLI for Sogni AI image and video generation.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is for legitimate media chunk parsing, not payload hiding. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Known maintainer rapid patch publish, no malicious indicator. | ai | |
| 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 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 3.18.0 | 4 / 6 | |
| 3.17.2 | 4 / 6 | |
| 3.17.1 | 4 / 6 | |
| 3.17.0 | 4 / 6 | |
| 3.16.1 | 4 / 6 | |
| 3.16.0 | 4 / 6 | |
| 3.15.1 | 4 / 6 | |
| 3.15.0 | 4 / 6 | |
| 3.14.1 | 4 / 6 | |
| 3.14.0 | 4 / 6 | |
| 3.13.0 | 4 / 6 | |
| 3.12.0 | 4 / 6 | |
| 3.11.1 | 4 / 6 | |
| 3.11.0 | 4 / 6 | |
| 3.10.0 | 4 / 6 | |
| 3.9.0 | 4 / 6 | |
| 3.8.0 | 4 / 6 | |
| 3.7.0 | 4 / 6 | |
| 3.6.4 | 4 / 6 | |
| 3.6.3 | 4 / 6 | |
| 3.6.2 | 4 / 6 | |
| 3.6.1 | 4 / 6 | |
| 3.6.0 | 4 / 6 | |
| 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.18.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krunkosaurus) than the most recent previously approved version (markledford) on 2026-07-27, 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.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krunkosaurus) than the most recent previously approved version (markledford) on 2026-07-26, 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.17.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (markledford) than the most recent previously approved version (krunkosaurus) on 2026-07-26, 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.16.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krunkosaurus) than the most recent previously approved version (markledford) on 2026-07-25, 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.16.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krunkosaurus) than the most recent previously approved version (markledford) on 2026-07-25, 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.15.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (markledford) than the most recent previously approved version (krunkosaurus) on 2026-07-22, 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.15.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krunkosaurus) than the most recent previously approved version (markledford) on 2026-07-21, 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.14.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (markledford) than the most recent previously approved version (krunkosaurus) on 2026-07-13, 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.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krunkosaurus) than the most recent previously approved version (markledford) on 2026-07-05, 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.10.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krunkosaurus) than the most recent previously approved version (markledford) on 2026-07-04, 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.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.