monocart-coverage-reports No license 42 versions

monocart-coverage-reports

npm Repository Homepage

42

Versions

—

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

cenfun

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:monocart-code-viewer	AI (dependencies): Same-author (cenfun) package; part of the monocart ecosystem.	ai	2026/06/03
dependencies	unvetted-dep:turbogrid	AI (dependencies): Same-author (cenfun) package with approved track record; stable dependency.	ai	2026/06/03
dependencies	unvetted-dep:monocart-formatter	AI (dependencies): Same-author (cenfun) package; part of the monocart ecosystem.	ai	2026/06/03
semgrep	semgrep:child-process-import	AI (semgrep): CLI binary legitimately uses child_process; stable pattern for this package.	ai	2026/06/03
semgrep	semgrep:child-process-spawn	AI (semgrep): CLI tool spawning subprocesses is expected; no malicious context in sample.	ai	2026/06/03
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Reflect.get in minified app bundle is a standard bundler output pattern, not obfuscation.	ai	2026/06/03
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	2026/05/14
semgrep	semgrep:base64-decode	AI (semgrep): Fires inside vendored bundle (PostCSS/template engine code); not a malicious payload pattern for this coverage tool.	ai	2026/05/14

Versions (showing 42 of 42)

Version	Deps	Published
2.12.11	12 / 46	2026-04-20
2.12.10	12 / 46	2026-04-15
2.12.9	12 / 44	2025-09-13
2.12.8	12 / 44	2025-09-11
2.12.7	12 / 44	2025-09-09
2.12.6	12 / 44	2025-05-15
2.12.5	12 / 44	2025-05-15
2.12.4	12 / 44	2025-04-14
2.12.3	12 / 44	2025-03-14
2.12.2	12 / 24	2025-02-26
2.12.1	12 / 24	2025-02-04
2.12.0	12 / 24	2025-01-20
2.11.6	12 / 25	2025-01-13
2.11.5	12 / 25	2024-12-18
2.11.4	12 / 26	2024-12-07
2.11.3	12 / 25	2024-11-21
2.11.2	12 / 25	2024-11-06
2.11.1	12 / 25	2024-10-07
2.11.0	12 / 25	2024-09-29
2.10.9	14 / 21	2024-09-17
2.10.8	14 / 21	2024-09-16
2.10.7	14 / 21	2024-09-16
2.10.6	14 / 21	2024-09-16
2.10.5	14 / 21	2024-09-15
2.10.4	14 / 21	2024-09-11
2.10.3	14 / 21	2024-08-14
2.10.2	14 / 21	2024-08-07
2.10.1	14 / 21	2024-08-05
2.10.0	14 / 21	2024-07-27
2.9.3	19 / 12	2024-07-18
2.9.2	19 / 12	2024-07-13
2.9.1	19 / 12	2024-07-08
2.9.0	10 / 14	2024-07-03
2.8.7	10 / 14	2024-07-01
2.8.6	10 / 14	2024-06-30
2.8.5	10 / 14	2024-06-21
2.8.4	10 / 13	2024-06-15
2.8.3	10 / 13	2024-05-26
2.8.2	10 / 12	2024-05-17
2.8.1	10 / 12	2024-05-11
2.8.0	10 / 12	2024-05-10
2.7.10	10 / 12	2024-05-01

v2.12.9

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

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

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

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

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

1 finding

LOW No provenance attestation provenance

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

v2.12.3

1 finding

LOW No provenance attestation provenance

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

v2.12.2

1 finding

LOW No provenance attestation provenance

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

v2.12.1

1 finding

LOW No provenance attestation provenance

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

v2.12.0

1 finding

LOW No provenance attestation provenance

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

v2.11.6

1 finding

LOW No provenance attestation provenance

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

v2.11.5

1 finding

LOW No provenance attestation provenance

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

v2.11.4

1 finding

LOW No provenance attestation provenance

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

v2.11.3

1 finding

LOW No provenance attestation provenance

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

v2.11.2

1 finding

LOW No provenance attestation provenance

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

v2.11.1

1 finding

LOW No provenance attestation provenance

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

v2.11.0

1 finding

LOW No provenance attestation provenance

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

v2.10.9

1 finding

LOW No provenance attestation provenance

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

v2.10.8

1 finding

LOW No provenance attestation provenance

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

v2.10.7

1 finding

LOW No provenance attestation provenance

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

v2.10.6

1 finding

LOW No provenance attestation provenance

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

v2.10.5

1 finding

LOW No provenance attestation provenance

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

v2.10.4

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

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.10.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.10.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.10.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.9.3

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.9.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.9.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.9.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.8.7

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

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

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

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

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.8.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.8.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.8.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.7.10

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.