third-party-web
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 |
|---|---|---|---|---|
| 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 |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.29.2 | 0 / 10 | |
| 0.29.0 | 0 / 10 | |
| 0.28.0 | 0 / 10 | |
| 0.24.5 | 0 / 10 | |
| 0.24.4 | 0 / 10 | |
| 0.24.3 | 0 / 10 | |
| 0.24.2 | 0 / 10 | |
| 0.24.1 | 0 / 10 | |
| 0.24.0 | 0 / 10 | |
| 0.23.4 | 0 / 10 | |
| 0.23.3 | 0 / 10 | |
| 0.23.2 | 0 / 10 | |
| 0.23.1 | 0 / 10 | |
| 0.23.0 | 0 / 10 | |
| 0.22.0 | 0 / 10 | |
| 0.21.0 | 0 / 10 | |
| 0.20.2 | 0 / 10 | |
| 0.20.1 | 0 / 10 | |
| 0.20.0 | 0 / 10 | |
| 0.19.0 | 0 / 10 | |
| 0.18.2 | 0 / 10 | |
| 0.18.1 | 0 / 10 | |
| 0.18.0 | 0 / 10 | |
| 0.17.1 | 0 / 10 | |
| 0.17.0 | 0 / 10 | |
| 0.16.0 | 0 / 10 | |
| 0.15.0 | 0 / 10 | |
| 0.14.0 | 0 / 10 | |
| 0.13.0 | 0 / 10 | |
| 0.12.7 | 0 / 7 | |
| 0.12.6 | 0 / 7 | |
| 0.12.5 | 0 / 7 | |
| 0.12.4 | 0 / 7 | |
| 0.12.3 | 0 / 7 | |
| 0.12.2 | 0 / 7 | |
| 0.12.1 | 0 / 8 | |
| 0.12.0 | 0 / 8 | |
| 0.11.1 | 0 / 8 | |
| 0.11.0 | 0 / 8 | |
| 0.10.1 | 0 / 8 | |
| 0.10.0 | 0 / 8 | |
| 0.9.0 | 0 / 8 | |
| 0.8.2 | 0 / 8 | |
| 0.8.1 | 0 / 8 | |
| 0.8.0 | 0 / 8 | |
| 0.7.0 | 0 / 8 | |
| 0.6.1 | 0 / 8 | |
| 0.6.0 | 0 / 8 | |
| 0.5.0 | 0 / 8 | |
| 0.4.0 | 0 / 6 | |
| 0.3.0 | 0 / 6 | |
| 0.2.0 | 0 / 5 | |
| 0.1.1 | 0 / 5 | |
| 0.1.0 | 0 / 4 |
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.