bcc/auto-mapper-bundle
Tests, a substantial README, and an MIT declaration provide useful adoption and licensing context. The repository is not archived, but its lone maintainer and absent security policy leave little evidence of current support.
42%
Total Score
25
70
50
Health Score Breakdown
The latest release was published in November 2017, with no releases in the past 12 months and a long median interval between releases, indicating substantial abandonment risk.
The repository recorded no commits and no active maintainers in the past three months, consistent with the release history showing that development has stopped.
Only one registry account has publishing access, leaving a thin publishing base; the linked repository is user-owned rather than organization-backed.
The repository name does not match the package name and its README does not mention the package, creating uncertainty about whether it is the intended source repository.
The repository has no security policy, so there is no documented channel or process for handling vulnerabilities in a package that has been inactive for years.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Michel Salib |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/property-access Version >=2.2.0 || ^3.0 | — | — |
symfony/framework-bundle Version >=2.2.0 || ^3.0 | — | — |
symfony/expression-language Version >=2.2.0 || ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 12 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.