@weibaohui/nothing-todo
NothingTodo - Rust CLI for managing your daily tasks
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Documented binary-selection postinstall for a Rust CLI distributed via platform-specific optional npm packages; stable pattern for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used to invoke the platform-specific prebuilt binary; expected for this native binary distribution pattern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.0.32 | 0 / 0 | |
| 0.0.28 | 0 / 0 | |
| 0.0.27 | 0 / 0 | |
| 0.0.26 | 0 / 0 | |
| 0.0.24 | 0 / 0 | |
| 0.0.18 | 0 / 0 | |
| 0.0.14 | 0 / 0 | |
| 0.0.12 | 0 / 0 | |
| 0.0.8 | 0 / 0 | |
| 0.0.5 | 0 / 0 | |
| 0.0.4 | 0 / 0 |
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
2 findingsScript: node install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
2 findingsScript: node install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
2 findingsScript: node install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
2 findingsScript: node install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
2 findingsScript: node install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
2 findingsScript: node install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
2 findingsScript: node install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
2 findingsScript: node install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
2 findingsScript: node install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.