flowpack/cors
Usable with caveats: it is a small, established package with tests, a clear README, organization backing, and a release for this version. Maintenance has slowed, with no releases in the last year and no commits in the last three months, while repository security hygiene is limited.
68%
Total Score
75
100
88
80
Health Score Breakdown
The package has existed since 2017 with six releases, but there have been no releases in the last 12 months and the median interval is about 187 days, indicating slow maintenance.
There were no commits and no active maintainers in the last three months, reinforcing the release-history concern and raising the risk that maintenance has stalled.
Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
No repository security policy was found, leaving vulnerability reporting guidance undocumented for consumers and contributors.
The CI workflow lacks top-level token permissions, so its permissions are not explicitly constrained; no workflow requests top-level write access.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 neos/flow Version ^8.3 || ^9.0 | — | — |
lmc/http-constants Version ^1.2 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.