MongoDB database access using immutables
62%
Total Score
caution
Usable with caveats: maintenance has stopped for over a year and workflow dependencies are unpinned.
The registry namespace and repository are owned by the same individual, which is consistent project backing for a small package. It also indicates a limited organizational maintainer base.
The package has 25 releases since September 2019, but no releases in the last 12 months; its latest release was over a year ago. That indicates a meaningful maintenance slowdown despite its earlier regular cadence.
The repository had zero commits and zero active maintainers in the last three months. Combined with the long release gap, this is evidence of paused maintenance and raises abandonment risk.
There are no open issues or pull requests, and no issue or pull request activity in the last month. This is neutral for a small stable project but provides no evidence of ongoing community maintenance.
Composer is used for the build, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap, not a severe risk by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version >=2.0.0 | — | — |
mbretter/stk-di Version >=2 | — | — |
mongodb/mongodb Version ~1.17|^2 | — | — |
mbretter/stk-immutable Version >=2 | — | — |
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.