@mochabug/adapt-sdk
The API toolkit to facilitate mochabug adapt plugin development
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Move to GitHub Actions CI publisher is a provenance improvement, not compromise. | ai | |
| source-diff | obfuscated-file:dist/cjs/browser.cjs | AI (source-diff): esbuild bundle output, not obfuscation; no malicious behavior in sample. | ai | |
| source-diff | obfuscated-file:dist/esm/signals.mjs | AI (source-diff): Bundled build output, same as cjs counterpart. | ai | |
| source-diff | encoded-string-file:dist/cjs/api.cjs | AI (source-diff): Long strings are generated protobuf/API symbol maps, not payloads. | ai | |
| source-diff | encoded-string-file:dist/esm/api.mjs | AI (source-diff): Same generated API bundle as cjs counterpart. | ai | |
| source-diff | obfuscated-file:dist/cjs/signals.cjs | AI (source-diff): Bundled jtd wrapper, minified build output. | ai | |
| source-diff | obfuscated-file:dist/esm/cel.mjs | AI (source-diff): Bundled build output, same as cjs counterpart. | ai | |
| source-diff | obfuscated-file:dist/esm/react.mjs | AI (source-diff): Bundled build output, same as cjs counterpart. | ai | |
| source-diff | obfuscated-file:dist/cjs/cel.cjs | AI (source-diff): Bundled @bufbuild/cel wrapper, minified build output. | ai | |
| source-diff | obfuscated-file:dist/cjs/react.cjs | AI (source-diff): Bundled fuse.js/react wrapper, minified build output. | ai | |
| source-diff | encoded-string-file:dist/esm/router.mjs | AI (source-diff): Same bufbuild protobuf descriptor pattern in ESM build; not obfuscation. | ai | |
| 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 | |
| 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 |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 0.4.24 | 6 / 13 | |
| 0.4.23 | 6 / 13 | |
| 0.4.22 | 6 / 13 | |
| 0.4.20 | 6 / 13 | |
| 0.4.19 | 6 / 13 | |
| 0.4.18 | 6 / 13 | |
| 0.4.17 | 6 / 13 | |
| 0.4.16 | 6 / 13 | |
| 0.4.15 | 6 / 12 | |
| 0.4.14 | 6 / 12 | |
| 0.4.13 | 6 / 12 | |
| 0.4.12 | 6 / 12 | |
| 0.4.11 | 6 / 12 | |
| 0.4.10 | 6 / 12 | |
| 0.4.9 | 6 / 12 | |
| 0.4.7 | 6 / 12 | |
| 0.4.6 | 6 / 12 | |
| 0.4.5 | 6 / 12 | |
| 0.4.3 | 6 / 12 | |
| 0.4.2 | 6 / 12 | |
| 0.4.1 | 6 / 12 | |
| 0.4.0 | 6 / 12 | |
| 0.3.12 | 6 / 11 | |
| 0.3.11 | 6 / 11 | |
| 0.3.10 | 6 / 11 | |
| 0.3.9 | 6 / 11 | |
| 0.3.7 | 6 / 11 | |
| 0.3.6 | 6 / 11 | |
| 0.3.5 | 6 / 11 | |
| 0.3.4 | 6 / 11 | |
| 0.3.3 | 6 / 11 | |
| 0.3.2 | 6 / 11 | |
| 0.3.1 | 6 / 11 | |
| 0.3.0 | 6 / 11 | |
| 0.2.9 | 6 / 11 | |
| 0.2.8 | 6 / 11 | |
| 0.2.7 | 6 / 11 | |
| 0.2.6 | 6 / 11 | |
| 0.2.5 | 6 / 11 | |
| 0.2.4 | 6 / 11 | |
| 0.2.3 | 6 / 11 | |
| 0.2.2 | 6 / 11 | |
| 0.2.1 | 6 / 11 | |
| 0.2.0 | 6 / 11 | |
| 0.1.25 | 3 / 10 | |
| 0.1.23 | 3 / 12 | |
| 0.1.22 | 3 / 12 | |
| 0.1.21 | 3 / 12 | |
| 0.1.20 | 3 / 12 | |
| 0.1.19 | 3 / 12 | |
| 0.1.18 | 3 / 12 |
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
11 findingsThis version was published by a different npm account than previous versions on 2026-02-09. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
4 findingsThis version was published by a different npm account than previous versions on 2026-02-02. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
3 findingsModified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
3 findingsModified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
3 findingsModified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
3 findingsModified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
3 findingsModified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
3 findingsModified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 22 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.