@mochabug/adapt-sdk — Greenflagged

The API toolkit to facilitate mochabug adapt plugin development

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

mikaelhedbergpatruf

Keywords

pluginmochabugadaptintelligent automationautomationartificial intelligence

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:dist/cjs/router.cjs	AI (source-diff): Long base64 strings are protobuf file descriptors generated by buf/bufbuild toolchain; stable pattern for this package.	ai	2026/05/10
source-diff	encoded-string-file:dist/esm/router.mjs	AI (source-diff): Same bufbuild protobuf descriptor pattern in ESM build; not obfuscation.	ai	2026/05/10
phantom-deps	phantom-dep:fuse.js	AI (phantom-deps): fuse.js is a declared runtime dependency; phantom-dep fires due to indirect import pattern, stable false positive for this SDK.	ai	2026/04/29

Versions (showing 19 of 19)

Version	Deps	Published
0.4.24	6 / 13	2026-04-30
0.4.23	6 / 13	2026-04-27
0.4.22	6 / 13	2026-04-11
0.4.20	6 / 13	2026-04-08
0.4.19	6 / 13	2026-04-07
0.4.18	6 / 13	2026-04-06
0.4.17	6 / 13	2026-04-06
0.4.16	6 / 13	2026-04-06
0.4.15	6 / 12	2026-04-06
0.4.12	6 / 12	2026-04-01
0.4.11	6 / 12	2026-04-01
0.4.10	6 / 12	2026-04-01
0.4.9	6 / 12	2026-04-01
0.4.7	6 / 12	2026-04-01
0.4.6	6 / 12	2026-04-01
0.4.5	6 / 12	2026-03-31
0.4.3	6 / 12	2026-03-31
0.4.1	6 / 12	2026-03-31
0.4.0	6 / 12	2026-03-31

v0.4.24

1 finding

LOW No provenance attestation provenance

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

v0.4.23

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.

v0.4.22

3 findings

HIGH Long encoded string in modified file: dist/cjs/router.cjs source-diff

Modified file contains 23 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/esm/router.mjs source-diff

Modified file contains 23 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.4.20

1 finding

LOW No provenance attestation provenance

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

v0.4.19

1 finding

LOW No provenance attestation provenance

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

v0.4.18

1 finding

LOW No provenance attestation provenance

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

v0.4.17

1 finding

LOW No provenance attestation provenance

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

v0.4.16

1 finding

LOW No provenance attestation provenance

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

v0.4.15

1 finding

LOW No provenance attestation provenance

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

v0.4.12

1 finding

LOW No provenance attestation provenance

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

v0.4.11

1 finding

LOW No provenance attestation provenance

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

v0.4.10

1 finding

LOW No provenance attestation provenance

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

v0.4.9

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.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.

v0.4.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.