Recent registry releases and a matching repository show ongoing publishing, with tests, documentation, and an MIT license. The single maintainer, no commits in the last three months, absent security policy, and unpinned workflow actions leave meaningful maintenance and build-hygiene concerns.
68%
Total Score
50
100
89
83
Only one registry account has publish access, creating a limited publishing and maintenance bus factor. The linked repository is also owned by a user rather than an organization, so no organizational backing compensates for that limitation.
There were no commits and no active maintainers in the last three months. Although a recent release provides some compensating evidence, the lack of current source activity is a real maintenance concern.
The repository has no stars or forks and only one watcher. This provides little external validation, but popularity is supporting evidence and does not by itself indicate the package is unsafe to adopt.
Composer is used as the build tool, but no security scanning tools were detected. For a package handling security tokens, the absent automated security tooling is a meaningful hygiene gap.
The repository has no security policy. That weakens vulnerability-reporting transparency for a package that provides security-token functionality.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
paragonie/paseto Version ^v3.1 | — | — |
delboy1978uk/barnacle Version ^2.5 | — | — |
boneframework/contracts Version ^1.7 | — | — |
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.