pkg-config
parse the closest `package.json` and get package specific configurations
5
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
ahmadnassri
Keywords
pkg-config
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): This package has intentionally used 0.0.0 since its initial publish ~11 years ago; it's a deliberate versioning choice, not a malware indicator. 188.9k weekly downloads confirm legitimacy. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): The dynamic require is the package's core functionality — reading the nearest package.json. Path is derived from find-root, not user input. Stable false positive for this package. | ai |