The small dependency surface and matching source repository make the package easy to inspect. No security policy is published, leaving less guidance for reporting issues, and the project shows little evidence of ongoing care.
42%
Total Score
50
100
75
75
This is the only release, published more than five years ago, with no releases in the last 12 months. That strongly raises abandonment risk for a dependency.
There were no commits or active maintainers in the last three months, consistent with the long release gap and providing little evidence of current maintenance.
The repository has no security policy, so users have no documented reporting path. This is a transparency and maintenance gap, but not a severe risk by itself.
Version 0.1.0 is not a stable major release, so its API maturity is limited; the absence of prerelease labeling does not offset that early development stage.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
bricks-framework/namespaced Version ^0.1|dev-master | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.