Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md | `changelog-v7-v13.md` | The full v7 -> v13 delta | 14 |
Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only Lance format reference; scanner alerts are about examples, mirrored docs, or formatting rather than hidden execution.
Installers should treat this as a reference skill, not an automation tool. Be careful when copying examples that delete files, overwrite datasets, use non-HTTPS or invalid certificate settings, place credentials in storage_options, or run cleanup with delete_unverified; use test paths and proper secret handling.
Referenced artifact was not completely inspected
| `changelog-v7-v13.md` | The full v7 -> v13 delta | 14 |
Referenced artifact was not completely inspected
| `changelog-v7-v13.md` | The full v7 -> v13 delta | 14 |
Referenced artifact was not completely inspected
| `changelog-v7-v13.md` | The full v7 -> v13 delta | 14 |
Referenced artifact was not completely inspected
| `changelog-v7-v13.md` | The full v7 -> v13 delta | 14 |
Referenced artifact was not completely inspected
| `changelog-v7-v13.md` | The full v7 -> v13 delta | 14 |
Referenced artifact was not completely inspected
| `changelog-v7-v13.md` | The full v7 -> v13 delta | 14 |
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
- **#8513 - re-compact.** "Execution applied that target again as a hard `max_rows_per_file`, so
each task above the target produced a full fragment followed by a small remainder that could
become isolated."
- **#8839 - chmod existing files.** Data and index files were created rejecting `group` and
`other` permissions, "which caused us trouble when using NFS"; the default is now 0o666. Files
already written keep their old mode.
- **#8904 - restart long-lived sessions.** The index metadata cache was keyed by dataset
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
This feature is currently experimental and not yet supported in any library.
<!-- TODO: When overlay file support is implemented, update this note to state
the released version that first supports the feature (and drop the
"experimental" framing once it is stable). -->
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
| `azure_object_id` / `object_id` | Object id for use with managed identity authentication. |
| `azure_msi_resource_id` / `msi_resource_id` | Msi resource id for use with managed identity authentication. |
| `azure_federated_token_file` / `federated_token_file` | File containing token for Azure AD workload identity federation. |
| `azure_use_azure_cli` / `use_azure_cli` | Use azure cli for acquiring access token. |
| `azure_disable_tagging` / `disable_tagging` | Disables tagging objects. This can be desirable if not supported by the backing store. |
## AliCloud Object Storage Service Configuration
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
| `azure_object_id` / `object_id` | Object id for use with managed identity authentication. |
| `azure_msi_resource_id` / `msi_resource_id` | Msi resource id for use with managed identity authentication. |
| `azure_federated_token_file` / `federated_token_file` | File containing token for Azure AD workload identity federation. |
| `azure_use_azure_cli` / `use_azure_cli` | Use azure cli for acquiring access token. |
| `azure_disable_tagging` / `disable_tagging` | Disables tagging objects. This can be desirable if not supported by the backing store. |
## AliCloud Object Storage Service Configuration
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
Now you'll write this dataframe to Lance format and verify the data was saved correctly:
shutil.rmtree("/tmp/test.lance", ignore_errors=True)
dataset = lance.write_dataset(df, "/tmp/test.lance")
dataset.to_table().to_pandas()
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
Now you'll write this dataframe to Lance format and verify the data was saved correctly:
shutil.rmtree("/tmp/test.lance", ignore_errors=True)
dataset = lance.write_dataset(df, "/tmp/test.lance")
dataset.to_table().to_pandas()
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
Now you'll write this dataframe to Lance format and verify the data was saved correctly:
shutil.rmtree("/tmp/test.lance", ignore_errors=True)
dataset = lance.write_dataset(df, "/tmp/test.lance")
dataset.to_table().to_pandas()
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
source schema is a strict subset of the target's and unmatched rows are kept, the builder
routes to `RewriteColumns` (a cheap column update) rather than rewriting whole fragments
(`rust/lance/src/dataset/write/merge_insert.rs:2232-2260`). Passing a full-schema source for
what is logically a two-column update therefore costs dramatically more, with no warning.
Project the source down to the key plus the columns actually being updated.
- **Local-filesystem durability is delegated, not added.** Lance's `file://` store is
`object_store::LocalFileSystem` (`rust/lance-io/src/object_store/providers/local.rs:26`,
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
source schema is a strict subset of the target's and unmatched rows are kept, the builder
routes to `RewriteColumns` (a cheap column update) rather than rewriting whole fragments
(`rust/lance/src/dataset/write/merge_insert.rs:2232-2260`). Passing a full-schema source for
what is logically a two-column update therefore costs dramatically more, with no warning.
Project the source down to the key plus the columns actually being updated.
- **Local-filesystem durability is delegated, not added.** Lance's `file://` store is
`object_store::LocalFileSystem` (`rust/lance-io/src/object_store/providers/local.rs:26`,
Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
The compression level is scheme dependent. Currently the following schemes support the following levels:
| Scheme | Crate Used | Levels | Default |
| ------ | --------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `zstd` | [`zstd`](https://crates.io/crates/zstd) | `0-22` | `crate dependent` (3 as of this writing) |
| `lz4` | [`lz4`](https://crates.io/crates/lz4) | N/A | The LZ4 crate has two modes (fast and high compression) and currently this is not exposed to configuration. The LZ4 crate wraps a C library and the default is dependent on the C library. The default as of this writing is fast |
Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
| Scheme | Crate Used | Levels | Default |
| ------ | --------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `zstd` | [`zstd`](https://crates.io/crates/zstd) | `0-22` | `crate dependent` (3 as of this writing) |
| `lz4` | [`lz4`](https://crates.io/crates/lz4) | N/A | The LZ4 crate has two modes (fast and high compression) and currently this is not exposed to configuration. The LZ4 crate wraps a C library and the default is dependent on the C library. The default as of this writing is fast |
Higher compression levels generally provide better compression at the cost of slower encoding speed. Decoding speed
Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
### Configuration
| Environment Variable | Default | Description |
|----------------------------|----------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| `LANCE_FTS_NUM_SHARDS` | Number of compute-intensive CPUs | Number of parallel tokenizer worker tasks. Higher values increase indexing throughput but use more memory. |
| `LANCE_FTS_PARTITION_SIZE` | 256 (MiB) | Maximum uncompressed size of a worker's in-memory buffer before it is spilled to a part file. |
Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
### Page File Schema
| Column | Type | Nullable | Description |
|:-------|:---------|:---------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `bbox` | RectType | false | Type is Rect defined by [geoarrow-rs](https://github.com/geoarrow/geoarrow-rs) RectType; physical storage is Struct<xmin: Float64, ymin: Float64, xmax: Float64, ymax: Float64>. Represents the node bounding box (leaf: item bbox; branch: child aggregation). |
| `id` | UInt64 | false | Reuse the `id` column to store `rowid` in leaf pages and `pageid` in branch pages |
Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
| Column | Type | Nullable | Description |
|:-------|:---------|:---------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `bbox` | RectType | false | Type is Rect defined by [geoarrow-rs](https://github.com/geoarrow/geoarrow-rs) RectType; physical storage is Struct<xmin: Float64, ymin: Float64, xmax: Float64, ymax: Float64>. Represents the node bounding box (leaf: item bbox; branch: child aggregation). |
| `id` | UInt64 | false | Reuse the `id` column to store `rowid` in leaf pages and `pageid` in branch pages |
### Nulls File Schema
The document makes conflicting guarantees about field ID behavior: it first says field IDs are immutable, unique, and stable, then later states dropped column IDs may be reused. In a format specification, this ambiguity is dangerous because independent implementations may make incompatible assumptions, leading to schema confusion, incorrect column resolution, corrupted reads, or authorization/integrity bugs in systems that rely on stable IDs for evolution and lineage.
Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
<div class="feature-flags-table" markdown="1">
| Flag Bit | Flag Name | Reader Required | Writer Required | Description |
|----------|---------------------------------|-----------------|-----------------|-------------------------------------------------------------------------------------------------------------|
| 1 | `FLAG_DELETION_FILES` | Yes | Yes | Fragments may contain deletion files, which record the tombstones of soft-deleted rows. |
| 2 | `FLAG_STABLE_ROW_IDS` | Yes | Yes | Row IDs are stable for both moves and updates. Fragments contain an index mapping row IDs to row addresses. |
Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.
These options apply to all object stores.
| Key | Description |
|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `allow_http` | Allow non-TLS, i.e. non-HTTPS connections. Default, `False`. |
| `download_retry_count` | Number of times to retry a download. Default, `3`. This limit is applied when the HTTP request succeeds but the response is not fully downloaded, typically due to a violation of `timeout`. |
Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.
These options apply to all object stores.
| Key | Description |
|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `allow_http` | Allow non-TLS, i.e. non-HTTPS connections. Default, `False`. |
| `download_retry_count` | Number of times to retry a download. Default, `3`. This limit is applied when the HTTP request succeeds but the response is not fully downloaded, typically due to a violation of `timeout`. |
Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
These options apply to all object stores.
| Key | Description |
|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `allow_http` | Allow non-TLS, i.e. non-HTTPS connections. Default, `False`. |
| `download_retry_count` | Number of times to retry a download. Default, `3`. This limit is applied when the HTTP request succeeds but the response is not fully downloaded, typically due to a violation of `timeout`. |
No suspicious patterns detected.