flexsearch
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:codacy-coverage | AI (dependencies): Legacy coverage-reporting dep, no runtime use. | ai | |
| phantom-deps | phantom-dep:codacy-coverage | AI (phantom-deps): Unused coverage tooling dep, not imported by design; stable false positive. | ai | |
| source-diff | obfuscated-file:coverage/prettify.js | AI (source-diff): Standard istanbul/nyc coverage report highlighter (prettify.js), minified vendor file; benign. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used for worker compilation of package's own logic, not attacker input. | ai | |
| source-diff | obfuscated-file:dist/module-min/charset/polyfill.js | AI (source-diff): Minified Unicode charset normalization table; build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/module-min/db/redis/db.js | AI (source-diff): Minified DB adapter build output, benign. | ai | |
| source-diff | obfuscated-file:dist/module-min/db/indexeddb/db.js | AI (source-diff): Minified DB adapter build output, matches build:db and declared devDeps. | ai | |
| source-diff | obfuscated-file:dist/module-min/db/mongodb/db.js | AI (source-diff): Minified DB adapter build output, benign. | ai | |
| source-diff | obfuscated-file:dist/module-min/db/postgres/db.js | AI (source-diff): Minified DB adapter build output, benign. | ai | |
| source-diff | obfuscated-file:dist/module-min/db/sqlite/db.js | AI (source-diff): Minified DB adapter build output, benign. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Worker config loader pattern, not attacker-controlled input; stable across versions. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): Dev build script only, not part of published runtime behavior. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Confined to dev build tooling (task/babel.js), not shipped runtime code. | ai |
Versions (showing 51 of 123)
| Version | Deps | Published |
|---|---|---|
| 0.8.212 | 0 / 27 | |
| 0.8.205 | 0 / 27 | |
| 0.8.204 | 0 / 27 | |
| 0.8.203 | 0 / 27 | |
| 0.8.202 | 0 / 27 | |
| 0.8.201 | 0 / 26 | |
| 0.8.200 | 0 / 26 | |
| 0.8.167 | 0 / 26 | |
| 0.8.166 | 0 / 26 | |
| 0.8.165 | 0 / 26 | |
| 0.8.164 | 0 / 26 | |
| 0.8.163 | 0 / 26 | |
| 0.8.162 | 0 / 26 | |
| 0.8.161 | 0 / 26 | |
| 0.8.160 | 0 / 26 | |
| 0.8.158 | 0 / 26 | |
| 0.8.157 | 0 / 26 | |
| 0.8.154 | 0 / 26 | |
| 0.8.153 | 0 / 26 | |
| 0.8.152 | 0 / 26 | |
| 0.8.151 | 0 / 26 | |
| 0.8.149 | 0 / 26 | |
| 0.8.148 | 0 / 26 | |
| 0.8.147 | 0 / 26 | |
| 0.8.143 | 0 / 26 | |
| 0.8.142 | 0 / 26 | |
| 0.8.141 | 0 / 26 | |
| 0.8.140 | 0 / 26 | |
| 0.8.138 | 0 / 26 | |
| 0.8.135 | 0 / 26 | |
| 0.8.132 | 0 / 26 | |
| 0.8.117 | 0 / 19 | |
| 0.8.105 | 0 / 22 | |
| 0.8.103 | 0 / 19 | |
| 0.8.1 | 0 / 19 | |
| 0.8.0 | 0 / 19 | |
| 0.7.43 | 0 / 18 | |
| 0.7.42 | 0 / 18 | |
| 0.7.41 | 0 / 18 | |
| 0.7.40 | 0 / 18 | |
| 0.7.39 | 0 / 18 | |
| 0.7.34 | 0 / 20 | |
| 0.7.33 | 0 / 20 | |
| 0.7.31 | 0 / 20 | |
| 0.7.21 | 0 / 20 | |
| 0.7.11 | 0 / 20 | |
| 0.7.3 | 0 / 20 | |
| 0.7.2 | 0 / 20 | |
| 0.7.1 | 0 / 19 | |
| 0.7.0 | 0 / 19 | |
| 0.6.32 | 0 / 9 |
v0.8.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.153
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.152
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.151
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.149
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.148
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.147
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.143
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.142
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.103
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.