← Home

@canonical/typescript-config-svelte

npm Repository Homepage

Canonical's standard TypeScript configuration for Svelte projects

22
Versions
LGPL-3.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ilayda21frankbanhuwshimianthonydillonsteverydzamylily1011bartazjpmartinsptpetesfrenchjmuzinamtrujedlerdabehniacanonical-organizationedisile-canonicalsteciuk-canonicalad.vlengr-aliando.gqninfa_jeonndv99goulin-canonicalimmortalcodesalvaromateoonibenjo-canonical

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from manual publish to GitHub Actions CI/CD; provenance direction is IMPROVED with SLSA attestation. ai
maintainer-change maintainer-removed AI (maintainer-change): mariadias143 removed as publisher was replaced by GitHub Actions CI/CD; consistent with org-level automation adoption. ai
phantom-deps phantom-dep:@canonical/typescript-config AI (phantom-deps): Declared as a runtime dependency in same org scope; heuristic false positive for a tsconfig-only package. ai
phantom-deps phantom-dep:@canonical/typescript-config-base AI (phantom-deps): tsconfig.json packages don't import deps via JS; phantom-dep is a stable false positive for this package type. ai

Versions (showing 22 of 22)

Version Deps Published
0.33.0 1 / 2
0.32.0 1 / 2
0.31.0 1 / 2
0.30.0 1 / 2
0.29.0 1 / 2
0.28.0 1 / 2
0.27.0 1 / 2
0.26.0 1 / 2
0.25.0 1 / 2
0.24.0 1 / 2
0.23.0 1 / 2
0.22.0 1 / 2
0.21.0 1 / 2
0.20.0 1 / 2
0.17.1 1 / 2
0.17.0 1 / 2
0.16.0 1 / 2
0.15.1 1 / 2
0.15.0 1 / 2
0.14.0 1 / 2
0.13.0 1 / 2
0.12.0 1 / 2

v0.33.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.32.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.31.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.30.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.29.0

2 findings
HIGH Publisher changed: mariadias143 → GitHub Actions (on 2026-07-03) provenance

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.20.0

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: ad.vl → mariadias143 (on 2026-03-26, known maintainer) provenance

This version was published by a different npm account (mariadias143) than the most recent previously approved version (ad.vl) on 2026-03-26, but mariadias143 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.17.1

1 finding
LOW No provenance attestation provenance

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

v0.17.0

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: jmuzina → ad.vl (on 2026-03-04, known maintainer) provenance

This version was published by a different npm account (ad.vl) than the most recent previously approved version (jmuzina) on 2026-03-04, but ad.vl 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.16.0

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: jmuzina → ad.vl (on 2026-03-03, known maintainer) provenance

This version was published by a different npm account (ad.vl) than the most recent previously approved version (jmuzina) on 2026-03-03, but ad.vl 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.15.1

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: jmuzina → ad.vl (on 2026-02-23, known maintainer) provenance

This version was published by a different npm account (ad.vl) than the most recent previously approved version (jmuzina) on 2026-02-23, but ad.vl 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.