Its dependencies are explicit, the repository is not archived, and the package maps directly to its source project. The small three-file project has no security policy, tests, or consumer documentation, limiting confidence in long-term maintenance.
57%
Total Score
75
50
78
67
The package has four named runtime dependencies and no development dependencies. The explicit dependency list is understandable, though the absence of development dependencies gives little evidence of local testing practices.
The package contains only three source or manifest files, which is plausible for a small bridge package but provides little visible project material for assessing maturity.
The artifact has no README, tests, or changelog. Missing tests and changelog are normal for published artifacts, but the missing README is a consumer-facing documentation gap for a library.
There were zero commits and zero active maintainers in the last three months. Combined with the lack of recent repository work, this is a meaningful maintenance concern, though the release history shows the project was previously active.
The repository has zero stars and forks and one watcher. This offers little adoption evidence, but popularity is supporting evidence rather than a health verdict.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version >= 2.8 | — | — |
doctrine/cache Version ^1.11 | — | — |
jadob/bridge-doctrine-dbal Version ^0.4.1 | — | — |
jadob/bridge-doctrine-persistence Version ^0.4.1 | — | — |
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.