@focus-mcp/brick-review MIT 2 versions

@focus-mcp/brick-review

npm Repository Homepage

Structured code review — analyze code quality, security, architecture patterns, compare versions.

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

samuelds

Keywords

mcpmodel-context-protocolaillmfocusbrickreviewcode-qualitysecurityarchitecturediff

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Signals reflect sparse metadata/packaging quality, not malicious behavior; no install scripts or suspicious code present.	ai	2026/04/28
provenance	no-provenance	AI (provenance): No provenance is common (~88% of npm packages); no other risk signals to amplify this.	ai	2026/04/28

Versions (showing 2 of 2)

Version	Deps	Published
1.1.0	0 / 0	2026-04-24
1.0.0	0 / 0	2026-04-23

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.