package-config
Get namespaced config from the closest package.json
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Transfer to sindresorhus is legitimate — repo moved to sindresorhus/package-config, package uses his standard toolchain, new deps are his own packages. Not a hijack. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to sindresorhus is a documented legitimate transfer; repo ownership and package content confirm authenticity. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy followed by a major-version rewrite under sindresorhus is consistent with a legitimate acquisition and modernization, not account takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): find-up-simple and load-json-file are both sindresorhus-authored packages, appropriate for this utility's purpose. | ai |
v5.0.0
3 findingsAll previous maintainers (leorossi) were replaced by new maintainers (sindresorhus). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2023-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.