@simplybusiness/mobius
Core library of Mobius react components
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): v9→v10 major version with new per-component dist structure explains the size increase. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/Checkbox/index.js | AI (source-diff): Standard esbuild CJS bundle output for a React component library. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/Combobox/Combobox.js | AI (source-diff): Standard esbuild CJS bundle output for a React component library. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/Combobox/index.js | AI (source-diff): Standard esbuild CJS bundle output for a React component library. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/DateField/DateField.js | AI (source-diff): Standard esbuild CJS bundle output for a React component library. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/DateField/index.js | AI (source-diff): Standard esbuild CJS bundle output for a React component library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version bump with per-component CJS split; size increase is structural, not injected. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/AddressLookup/AddressLookup.js | AI (source-diff): Standard esbuild CJS bundle with readable source paths and matching sourcemaps; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/AddressLookup/index.js | AI (source-diff): Standard esbuild CJS bundle output; long lines from bundled deps, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/Checkbox/Checkbox.js | AI (source-diff): Standard esbuild CJS bundle output for a React component library. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/Checkbox/CheckboxGroup.js | AI (source-diff): Standard esbuild CJS bundle output for a React component library. | ai | |
| source-diff | obfuscated-file:dist/cjs/index.js | AI (source-diff): Standard esbuild CJS bundle output; long lines are bundler boilerplate, not obfuscation. Stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@simplybusiness/mobius-hooks | AI (dependencies): First-party Simply Business package; companion hooks library for mobius. | ai | |
| dependencies | unvetted-dep:dialog-polyfill | AI (dependencies): Well-known Google-maintained polyfill; low risk. | ai | |
| dependencies | unvetted-dep:react-accessible-dropdown-menu-hook | AI (dependencies): Established accessibility hook library; no known issues. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Intentional for this org's internal component library published to public npm. | ai | |
| dependencies | unvetted-dep:@simplybusiness/icons | AI (dependencies): First-party Simply Business package; expected dependency for this org's component library. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 10.6.0 | 8 / 28 | |
| 10.5.0 | 8 / 28 | |
| 10.4.4 | 8 / 28 | |
| 10.4.3 | 8 / 27 | |
| 10.4.2 | 9 / 27 | |
| 10.4.1 | 9 / 27 | |
| 10.4.0 | 9 / 27 | |
| 10.3.4 | 9 / 27 | |
| 10.3.3 | 9 / 27 | |
| 10.3.2 | 9 / 27 | |
| 10.3.1 | 9 / 27 | |
| 10.3.0 | 9 / 27 | |
| 9.2.0 | 9 / 27 | |
| 9.1.2 | 9 / 27 | |
| 9.1.1 | 9 / 27 | |
| 9.1.0 | 9 / 27 | |
| 9.0.2 | 8 / 27 | |
| 9.0.1 | 8 / 27 | |
| 9.0.0 | 8 / 27 | |
| 8.0.2 | 8 / 33 | |
| 8.0.1 | 8 / 33 | |
| 8.0.0 | 8 / 33 | |
| 7.1.3 | 8 / 33 | |
| 7.1.2 | 8 / 33 | |
| 7.1.1 | 8 / 33 | |
| 7.1.0 | 8 / 33 | |
| 7.0.0 | 7 / 33 | |
| 6.10.5 | 7 / 33 | |
| 6.10.4 | 7 / 33 | |
| 6.10.3 | 7 / 33 | |
| 6.10.2 | 7 / 33 | |
| 6.10.1 | 7 / 33 | |
| 6.10.0 | 7 / 33 | |
| 6.9.10 | 7 / 33 | |
| 6.9.9 | 7 / 33 | |
| 6.9.8 | 7 / 33 | |
| 6.9.7 | 7 / 33 | |
| 6.9.6 | 7 / 33 | |
| 6.9.5 | 7 / 33 | |
| 6.9.4 | 7 / 33 | |
| 6.9.3 | 7 / 33 | |
| 6.9.2 | 7 / 33 | |
| 6.9.1 | 7 / 33 | |
| 6.9.0 | 7 / 33 | |
| 6.8.1 | 7 / 33 | |
| 6.8.0 | 7 / 33 | |
| 6.7.2 | 7 / 34 | |
| 6.7.1 | 7 / 34 | |
| 6.7.0 | 7 / 34 | |
| 6.6.0 | 7 / 34 | |
| 6.5.5 | 7 / 34 |
v10.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.2
10 findingsNewly 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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
10 findingsNewly 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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
10 findingsNewly 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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.