static-injector
Supply chain provenance
Status for the latest visible version.
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): New maintainer wszgrcy matches repo owner and package author; consistent with legitimate ownership transfer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): wszgrcy is the documented author/repo owner; addition is expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): cyia removed as part of ownership transfer to wszgrcy; consistent with repo history. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI/CD with SLSA attestation; consistent with legitimate maintainer transition. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.4.0 | 0 / 0 | |
| 6.3.1 | 0 / 0 | |
| 6.3.0 | 0 / 0 | |
| 6.2.0 | 0 / 0 | |
| 6.1.2 | 0 / 0 | |
| 6.1.1 | 0 / 0 | |
| 6.1.0 | 0 / 0 | |
| 3.0.0 | 0 / 0 |
v6.4.0
3 findingsAll previous maintainers (cyia) were replaced by new maintainers (wszgrcy). 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 2026-06-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.1
3 findingsAll previous maintainers (cyia) were replaced by new maintainers (wszgrcy). 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 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
3 findingsAll previous maintainers (cyia) were replaced by new maintainers (wszgrcy). 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 2025-06-10. 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.
v6.1.1
3 findingsAll previous maintainers (cyia) were replaced by new maintainers (wszgrcy). 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 2025-06-09. 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.
v6.1.0
3 findingsAll previous maintainers (cyia) were replaced by new maintainers (wszgrcy). 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 2025-06-08. 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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.