third-party-web
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
patrickhulce
Keywords
third-partythird-parties
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from patrickhulce to GitHub Actions is consistent with CI/CD automation; SLSA attestation confirms legitimate pipeline publish. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-attested publish is low risk; SLSA provenance confirms supply chain integrity. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in a test file loading built output files; not a runtime code path. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package's core content is third-party web entity data with many URLs; README link density is expected, not spam. | ai |
v0.29.2
2 findings
HIGH
Publisher changed: patrickhulce → GitHub Actions (on 2026-05-14)
provenance
This version was published by a different npm account than previous versions on 2026-05-14. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.