← Home

@telegraph/toggle

npm Repository

Toggle component for Telegraph

11
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
provenance publisher-changed AI (provenance): cjbell is a @knocklabs org member with 177 approved packages; transition from kylemcd appears to be a legitimate internal handoff. ai
dependencies unvetted-dep:@telegraph/icon AI (dependencies): Internal sibling package from the same knocklabs/telegraph monorepo. ai
dependencies unvetted-dep:@telegraph/button AI (dependencies): Internal sibling package from the same knocklabs/telegraph monorepo. ai
dependencies unvetted-dep:@telegraph/tag AI (dependencies): Internal sibling package from the same knocklabs/telegraph monorepo. ai
dependencies unvetted-dep:@telegraph/helpers AI (dependencies): Internal sibling package from the same knocklabs/telegraph monorepo. ai
dependencies unvetted-dep:@telegraph/typography AI (dependencies): Internal sibling package from the same knocklabs/telegraph monorepo. ai
dependencies unvetted-dep:@telegraph/layout AI (dependencies): Internal sibling package from the same knocklabs/telegraph monorepo. ai

Versions (showing 11 of 11)

Version Deps Published
0.1.6 9 / 11
0.1.5 9 / 11
0.1.4 9 / 11
0.1.3 9 / 11
0.1.2 9 / 11
0.1.1 9 / 11
0.1.0 9 / 11
0.0.5 9 / 11
0.0.4 9 / 11
0.0.3 9 / 11
0.0.2 9 / 11

v0.1.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: cjbell → kylemcd (on 2026-06-09, known maintainer) provenance

This version was published by a different npm account (kylemcd) than the most recent previously approved version (cjbell) on 2026-06-09, but kylemcd is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: cjbell → kylemcd (on 2026-06-05, known maintainer) provenance

This version was published by a different npm account (kylemcd) than the most recent previously approved version (cjbell) on 2026-06-05, but kylemcd is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.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.1.3

2 findings
HIGH Publisher changed: kylemcd → cjbell (on 2026-04-09) provenance

This version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.2

2 findings
HIGH Publisher changed: kylemcd → cjbell (on 2026-04-08) provenance

This version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.1

2 findings
HIGH Publisher changed: kylemcd → cjbell (on 2026-03-12) provenance

This version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.

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.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

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.