@moneko/solid
Solid js
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 | obfuscated-file:dev/mdx.js | AI (source-diff): Minified build output with inline source map; code is readable SolidJS MDX provider, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:lib/mdx.js | AI (source-diff): Same minified build artifact as dev/mdx.js; stable pattern for this package's build pipeline. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package with 102 versions and consistent downloads; sparse metadata is a style choice, not spam. | ai | |
| phantom-deps | phantom-dep:solid-refresh | AI (phantom-deps): Referenced in build config only; not a runtime import. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-jsx-dom-expressions | AI (phantom-deps): Build/config-only reference; not a direct runtime import. Stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.2.2 | 3 / 6 | |
| 2.2.0 | 3 / 6 | |
| 2.1.2 | 3 / 6 | |
| 2.1.1 | 3 / 6 | |
| 2.1.0 | 3 / 6 | |
| 2.0.3 | 3 / 5 | |
| 2.0.2 | 3 / 5 | |
| 2.0.1 | 3 / 5 | |
| 2.0.0 | 3 / 4 |
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.