← Home

@kie-tools/unitables

<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to

2
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

kie-tools-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:ajv AI (phantom-deps): ajv is referenced in config files (webpack/babel); not a direct import but legitimately declared. ai
phantom-deps phantom-dep:ajv-errors AI (phantom-deps): Same as ajv — config-file usage, not a phantom dep concern. ai
phantom-deps phantom-dep:react-table AI (phantom-deps): Type-only or indirect usage in a React UI library; stable false positive. ai
phantom-deps phantom-dep:@types/lodash AI (phantom-deps): Type package loaded by convention; expected for TypeScript projects. ai
phantom-deps phantom-dep:@types/react-table AI (phantom-deps): Type package loaded by convention; expected for TypeScript projects. ai
phantom-deps phantom-dep:@kie-tools-core/notifications AI (phantom-deps): Sibling monorepo package; config-file reference is expected. ai
provenance no-provenance AI (provenance): Apache KIE Tools CI bot publishes without Sigstore provenance; consistent across all versions. ai

Versions (showing 2 of 2)

Version Deps Published
10.2.0 23 / 11
10.1.0 23 / 11

v10.2.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.

v10.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.