Enables developers to use a unified Postman Collection format Object across projects
78%
Total Score
63
100
100
67
50
No registry build attestation or trusted-publisher provenance is present, leaving publication origin less verifiable. The matching organization-owned repository and long release history provide partial context but do not replace attestations.
All 3 recent commits came from one contributor, creating concentration risk. Organization ownership provides some capacity to hand maintenance off, so this is a caution rather than a severe liability.
Only 3 commits were made in the last 3 months, indicating light recent development. The current release cadence and recent repository push show that the project has not been abandoned.
There were no new or closed issues in the last month, while pull-request activity was limited and no pull requests were merged. This is a mild maintenance concern, though recent commits and releases provide compensating evidence.
No repository security policy was found, leaving vulnerability reporting and response expectations less transparent. The configured security scanning tools partly compensate for this gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mime Version 3.0.0 | — | — |
uuid Version 8.3.2 | — | — |
lodash Version 4.18.1 | — | — |
semver Version 7.7.1 | — | — |
file-type Version 3.9.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.