ASN.1 schema for PKCS #10 certificate signing requests defined in RFC 2986.
78%
Total Score
healthy
Active organization-backed project with strong release evidence, but all workflow actions are unpinned and repository linkage is indirect.
The repository name does not match the package and its README does not mention it, so the package-to-repository link is indirect. Because this is an organization-owned monorepo, the mismatch is plausible but still reduces transparency.
The project uses TypeScript, Vitest, and npm scripts, but no security-scanning tools were detected. The build tooling is solid; the missing scanning is a modest hygiene gap.
No repository security policy was found. This reduces transparency for reporting vulnerabilities, although active maintenance and organization backing partly compensate.
All nine analyzed action references are unpinned, which weakens build reproducibility. The audit also found high-confidence template-injection patterns in release.yml; under the stated rules these are workflow hygiene concerns without an untrusted trigger or sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tslib Version ^2.8.1 | — | — |
asn1js Version ^3.0.10 | — | — |
@peculiar/asn1-x509 Version ^2.11.0 | — | — |
@peculiar/asn1-schema Version ^2.11.0 | — | — |
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.