@mybricks/sdk-for-app
SDK for application UI
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 |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): Intentional remote script execution pattern in a low-code SDK; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 314 versions; lack of Sigstore attestation is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:dom-to-image | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:html-to-image | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:html-webpack-plugin | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:compare-versions | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:form-data | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.0.77 | 6 / 33 | |
| 1.0.75 | 6 / 33 | |
| 1.0.74 | 6 / 33 | |
| 1.0.73 | 6 / 33 | |
| 1.0.72 | 6 / 33 | |
| 1.0.71 | 6 / 33 | |
| 1.0.70 | 6 / 33 | |
| 1.0.69 | 6 / 33 | |
| 1.0.68 | 6 / 33 | |
| 1.0.67 | 6 / 33 | |
| 1.0.66 | 6 / 33 | |
| 1.0.65 | 6 / 33 | |
| 1.0.64 | 6 / 33 | |
| 1.0.63 | 6 / 33 |
v1.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.