@easyops-cn/docusaurus-search-local
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Popular plugin with 245k weekly downloads; README/keyword signals are false positives for this package. | ai | |
| dependencies | unvetted-dep:lunr-languages | AI (dependencies): Standard multilingual search dependency for a Docusaurus search plugin; expected and stable. | ai | |
| dependencies | unvetted-dep:@easyops-cn/autocomplete.js | AI (dependencies): First-party autocomplete fork maintained by the same org; expected dependency for this package. | ai |
Versions (showing 30 of 130)
| Version | Deps | Published |
|---|---|---|
| 0.14.2 | 11 / 39 | |
| 0.14.1 | 11 / 39 | |
| 0.14.0 | 11 / 39 | |
| 0.13.1 | 11 / 40 | |
| 0.13.0 | 11 / 40 | |
| 0.12.0 | 10 / 40 | |
| 0.11.2 | 10 / 40 | |
| 0.11.1 | 10 / 40 | |
| 0.11.0 | 10 / 40 | |
| 0.10.1 | 9 / 35 | |
| 0.10.0 | 9 / 35 | |
| 0.9.4 | 8 / 35 | |
| 0.9.3 | 8 / 35 | |
| 0.9.2 | 8 / 35 | |
| 0.9.0 | 8 / 34 | |
| 0.8.0 | 6 / 32 | |
| 0.7.1 | 6 / 32 | |
| 0.7.0 | 6 / 32 | |
| 0.6.2 | 7 / 31 | |
| 0.6.1 | 7 / 31 | |
| 0.6.0 | 7 / 31 | |
| 0.5.3 | 7 / 31 | |
| 0.5.2 | 7 / 30 | |
| 0.5.1 | 7 / 30 | |
| 0.4.5 | 7 / 11 | |
| 0.4.4 | 7 / 11 | |
| 0.4.3 | 6 / 11 | |
| 0.4.2 | 6 / 11 | |
| 0.4.1 | 6 / 11 | |
| 0.4.0 | 6 / 11 |
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
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.1
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
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.2
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.