Clear licensing, repository tests, and no install-time scripts reduce adoption risk. The project has no security policy or scanning, and its legacy documentation says it is not fully ready, making this old release a liability.
42%
Total Score
0
100
63
83
The package has had no releases in the last 12 months, and its latest release was about seven years ago. This strongly suggests the release is no longer actively maintained.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the last release and indicating substantial abandonment risk.
The artifact includes a substantial README and changelog, while the repository has tests and a changelog. The README explicitly describes the classes as legacy and not fully ready, limiting the otherwise positive documentation signal.
The repository name matches the package, but the package name is not mentioned in its README. That weakens confidence that the repository documentation directly identifies this package.
Composer build tooling is present, but no security-scanning tools are reported. Given the project's long inactivity, this missing security process adds a modest hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tecnickcom/tc-lib-barcode Version ^1.15 | — | — |
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.