Text and chat template tools used by Instructor library
70%
Total Score
caution
Frequent releases and active repository work support adoption, but all recent commits come from one contributor.
One contributor made all 13 commits in the last 3 months, creating a genuine continuity risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.
Composer is used as the build tool, but no repository security scanning tools were detected. The missing scanning is a maintenance and transparency gap, though not severe on its own.
No repository security policy was found, leaving vulnerability-reporting expectations undocumented. This is a real transparency gap but does not by itself make the release unfit.
The single workflow was fully analyzed with no audit findings, no untrusted checkout or script-injection sink, and no top-level write permissions. Its one action is unpinned, which is a supply-chain hygiene weakness; the pull_request_target trigger is ordinary without a dangerous sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cognesy/instructor-utils Version ^2.14 | — | — |
cognesy/instructor-config Version ^2.14 | — | — |
cognesy/instructor-messages Version ^2.14 | — | — |
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.