← Home

@telegraph/data-list

npm Repository

Flexible data list component for displaying label-value pairs in a structured, composable format.

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kylemcdcjbell

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@telegraph/icon AI (dependencies): Internal sibling package from knocklabs/telegraph monorepo; stable false positive for this package family. ai
dependencies unvetted-dep:@telegraph/layout AI (dependencies): Internal sibling package from knocklabs/telegraph monorepo; stable false positive for this package family. ai
dependencies unvetted-dep:@telegraph/helpers AI (dependencies): Internal sibling package from knocklabs/telegraph monorepo; stable false positive for this package family. ai
dependencies unvetted-dep:@telegraph/tooltip AI (dependencies): Internal sibling package from knocklabs/telegraph monorepo; stable false positive for this package family. ai
dependencies unvetted-dep:@telegraph/typography AI (dependencies): Internal sibling package from knocklabs/telegraph monorepo; stable false positive for this package family. ai

Versions (showing 12 of 12)

Version Deps Published
0.2.1 5 / 11
0.1.1 5 / 11
0.1.0 5 / 11
0.0.9 5 / 11
0.0.8 5 / 11
0.0.7 5 / 11
0.0.6 5 / 11
0.0.5 5 / 11
0.0.4 4 / 11
0.0.3 4 / 11
0.0.2 4 / 11
0.0.1 4 / 11

v0.2.1

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.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.9

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.

v0.0.8

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.

v0.0.7

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.

v0.0.6

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.

v0.0.5

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.

v0.0.4

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.

v0.0.3

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.

v0.0.2

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.

v0.0.1

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.