monocart-coverage-reports
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-specified config file path in CLI, standard pattern. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Bundled vendor lib pattern, no exfil destination present. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): CLI tool spawning subprocesses is expected; no malicious context in sample. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get in minified app bundle is a standard bundler output pattern, not obfuscation. | ai | |
| dependencies | unvetted-dep:monocart-formatter | AI (dependencies): Same-author (cenfun) package; part of the monocart ecosystem. | ai | |
| dependencies | unvetted-dep:monocart-code-viewer | AI (dependencies): Same-author (cenfun) package; part of the monocart ecosystem. | ai | |
| dependencies | unvetted-dep:turbogrid | AI (dependencies): Same-author (cenfun) package with approved track record; stable dependency. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI binary legitimately uses child_process; stable pattern for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires inside vendored bundle (PostCSS/template engine code); not a malicious payload pattern for this coverage tool. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in vendored bundle is standard template engine/parser pattern; stable false positive for this package. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 2.12.11 | 12 / 46 | |
| 2.12.10 | 12 / 46 | |
| 2.12.9 | 12 / 44 | |
| 2.12.8 | 12 / 44 | |
| 2.12.7 | 12 / 44 | |
| 2.12.6 | 12 / 44 | |
| 2.12.5 | 12 / 44 | |
| 2.12.4 | 12 / 44 | |
| 2.12.3 | 12 / 44 | |
| 2.12.2 | 12 / 24 | |
| 2.12.1 | 12 / 24 | |
| 2.12.0 | 12 / 24 | |
| 2.11.6 | 12 / 25 | |
| 2.11.5 | 12 / 25 | |
| 2.11.4 | 12 / 26 | |
| 2.11.3 | 12 / 25 | |
| 2.11.2 | 12 / 25 | |
| 2.11.1 | 12 / 25 | |
| 2.11.0 | 12 / 25 | |
| 2.10.9 | 14 / 21 | |
| 2.10.8 | 14 / 21 | |
| 2.10.7 | 14 / 21 | |
| 2.10.6 | 14 / 21 | |
| 2.10.5 | 14 / 21 | |
| 2.10.4 | 14 / 21 | |
| 2.10.3 | 14 / 21 | |
| 2.10.2 | 14 / 21 | |
| 2.10.1 | 14 / 21 | |
| 2.10.0 | 14 / 21 | |
| 2.9.3 | 19 / 12 | |
| 2.9.2 | 19 / 12 | |
| 2.9.1 | 19 / 12 | |
| 2.9.0 | 10 / 14 | |
| 2.8.7 | 10 / 14 | |
| 2.8.6 | 10 / 14 | |
| 2.8.5 | 10 / 14 | |
| 2.8.4 | 10 / 13 | |
| 2.8.3 | 10 / 13 | |
| 2.8.2 | 10 / 12 | |
| 2.8.1 | 10 / 12 | |
| 2.8.0 | 10 / 12 | |
| 2.7.10 | 10 / 12 | |
| 2.7.9 | 10 / 12 | |
| 2.7.8 | 10 / 12 | |
| 2.7.7 | 9 / 12 | |
| 2.7.6 | 9 / 12 | |
| 2.7.5 | 9 / 12 | |
| 2.7.4 | 9 / 12 | |
| 2.7.3 | 9 / 12 | |
| 2.7.2 | 9 / 11 | |
| 2.7.1 | 9 / 10 | |
| 2.7.0 | 9 / 10 | |
| 2.6.5 | 9 / 9 | |
| 2.6.4 | 9 / 9 | |
| 2.6.3 | 9 / 9 | |
| 2.6.2 | 9 / 9 | |
| 2.6.1 | 9 / 9 | |
| 2.6.0 | 9 / 9 | |
| 2.5.9 | 9 / 9 | |
| 2.5.8 | 9 / 9 | |
| 2.5.7 | 9 / 9 | |
| 2.5.6 | 9 / 9 | |
| 2.5.5 | 9 / 8 | |
| 2.5.4 | 9 / 8 | |
| 2.5.3 | 9 / 8 | |
| 2.5.2 | 9 / 7 | |
| 2.5.1 | 9 / 7 | |
| 2.5.0 | 9 / 7 | |
| 2.4.4 | 9 / 7 | |
| 2.4.3 | 9 / 7 | |
| 2.4.2 | 9 / 7 | |
| 2.4.1 | 9 / 7 | |
| 2.4.0 | 9 / 7 | |
| 2.3.4 | 9 / 7 | |
| 2.3.3 | 9 / 7 | |
| 2.3.2 | 9 / 7 | |
| 2.3.1 | 9 / 7 | |
| 2.3.0 | 9 / 7 | |
| 2.2.2 | 9 / 7 | |
| 2.2.1 | 9 / 7 | |
| 2.2.0 | 9 / 7 | |
| 2.1.0 | 9 / 6 | |
| 2.0.10 | 9 / 6 | |
| 2.0.9 | 9 / 6 | |
| 2.0.8 | 9 / 6 | |
| 2.0.7 | 9 / 6 | |
| 2.0.6 | 9 / 6 | |
| 2.0.5 | 9 / 6 | |
| 2.0.4 | 9 / 7 | |
| 2.0.3 | 9 / 7 | |
| 2.0.2 | 9 / 7 | |
| 2.0.1 | 9 / 7 | |
| 2.0.0 | 9 / 7 |
v2.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.