@fugood/bricks-ctor
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established publisher; missing description is low-risk metadata issue. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is optional; publisher has strong track record. | ai | |
| dependencies | unvetted-dep:@huggingface/gguf | AI (dependencies): @huggingface/gguf is a legitimate HuggingFace library; stable dependency for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped private/internal package; missing metadata is consistent with org-internal tooling, not spam. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Passing process.env to child Electron process is standard dev-tool pattern. | ai | |
| phantom-deps | phantom-dep:@fugood/bricks-cli | AI (phantom-deps): Same-org CLI companion; likely used via bin or indirect require. | ai | |
| phantom-deps | phantom-dep:@types/bun | AI (phantom-deps): @types packages are ambient type declarations, not runtime imports. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): @types packages are ambient type declarations, not runtime imports. | ai | |
| phantom-deps | phantom-dep:@types/escodegen | AI (phantom-deps): @types packages are ambient type declarations, not runtime imports. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.24.6 | 14 / 0 | |
| 2.24.5 | 14 / 0 | |
| 2.24.4 | 14 / 0 | |
| 2.24.3 | 14 / 0 | |
| 2.24.2 | 14 / 0 | |
| 2.24.1 | 14 / 0 | |
| 2.24.0 | 13 / 0 |
v2.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
2 findingsSpreading entire process.env into an object — may capture all secrets 114 | ['--bun', 'electron', `${import.meta.dirname}/preview-main.mjs`, ...args], 115 | { > 116 | env: { ...process.env, BRICKS_STAGE: app.stage || 'production' }, 117 | stdio: ['inherit', 'pipe', 'inherit'], 118 | },
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
2 findingsSpreading entire process.env into an object — may capture all secrets 108 | 109 | const proc = Bun.spawn(['bunx', '--bun', 'electron', `${__dirname}/preview-main.mjs`, ...args], { > 110 | env: { ...process.env, BRICKS_STAGE: app.stage || 'production' }, 111 | stdout: 'pipe', 112 | stderr: 'inherit',
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.