← Home

@degausai/wonda

npm Repository Homepage

AI-powered content generation CLI

12
Versions
Proprietary
License
Yes
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

andudududu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): child_process used in install.js to invoke platform binary selection; consistent with prebuilt binary distribution. ai
install-scripts install-script:postinstall AI (install-scripts): Postinstall selects prebuilt platform binaries via optional deps; standard native CLI distribution pattern. ai

Versions (showing 12 of 12)

Version Deps Published
1.25.0 0 / 0
1.20.0 0 / 0
1.17.0 0 / 0
1.14.0 0 / 0
1.13.1 0 / 0
1.12.0 0 / 0
1.7.1 0 / 0
1.7.0 0 / 0
1.6.0 0 / 0
1.4.0 0 / 0
1.2.0 0 / 0
1.0.0 0 / 0

v1.25.0

1 finding
LOW No provenance attestation provenance

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

v1.20.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.17.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.14.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.13.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.12.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.7.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.7.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.6.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.4.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.2.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.

v1.0.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.