blaspsoft/doxswap
The project has strong test coverage, a substantial README, and a matching organization-backed repository. Its small release history, no recent commits, absent security policy, and unpinned workflow actions leave meaningful maintenance and build-hygiene concerns.
62%
Total Score
67
100
89
75
Health Score Breakdown
Only two releases have been published across roughly 18 months, with one release in the last 12 months and a median interval of about 7 months. This indicates a modest maintenance cadence rather than active development.
There were no commits and no active maintainers in the last 3 months. Combined with the slow release history, this is a meaningful sign of currently quiet maintenance.
The repository has five open issues, one open pull request, and no issue or pull-request activity in the last month. This suggests limited recent project interaction, though the backlog is small.
Composer build tooling is present, but no security scanning tools were detected. That is a modest repository hygiene gap, not evidence that the release is unsafe by itself.
The repository has no security policy. For a package that processes documents and images, this reduces transparency around vulnerability reporting and response.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Michael Deeming |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 blaspsoft/onym Version ^1.0 | — | — |
illuminate/support Version ^8.0|^9.0|^10.0|^11.0|^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 11 months ago
- Created
- 1 year 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.