← Home

@canonical/react-ds-app-anbox

npm Repository Homepage

Anbox-specific components for the Pragma design system

14
Versions
LGPL-3.0
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

ilayda21frankbanhuwshimianthonydillonsteverydzamylily1011bartazjpmartinsptpetesfrenchmariadias143jmuzinamtrujedlerdabehniacanonical-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): jmuzina is a trusted publisher (156/0 record) within the canonical org; transition appears legitimate. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer rotation within canonical org; no malicious indicators in code or metadata. ai
phantom-deps phantom-dep:@canonical/styles AI (phantom-deps): Same-org monorepo dep; used transitively/re-exported, not directly imported. ai
phantom-deps phantom-dep:@canonical/react-ds-global AI (phantom-deps): Same-org monorepo dep; used transitively/re-exported, not directly imported. ai
phantom-deps phantom-dep:@canonical/storybook-config AI (phantom-deps): Same-org monorepo dep; used via config, not directly imported in source. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): Peer/config-level usage; stable false positive for this package. ai

Versions (showing 14 of 14)

Version Deps Published
0.27.0 5 / 22
0.26.0 5 / 23
0.25.0 5 / 23
0.24.0 5 / 23
0.23.0 5 / 23
0.22.0 5 / 23
0.21.0 5 / 23
0.20.0 5 / 22
0.17.1 5 / 22
0.17.0 5 / 22
0.16.0 5 / 22
0.15.1 5 / 22
0.15.0 5 / 22
0.11.0 5 / 19

v0.27.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.

v0.26.0

1 finding
LOW No provenance attestation provenance

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

v0.25.0

1 finding
LOW No provenance attestation provenance

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

v0.24.0

1 finding
LOW No provenance attestation provenance

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

v0.23.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.

v0.22.0

2 findings
HIGH Publisher changed: ad.vl → mariadias143 (on 2026-04-03) provenance

This version was published by a different npm account than previous versions on 2026-04-03. 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.21.0

2 findings
HIGH Publisher changed: ad.vl → mariadias143 (on 2026-04-01) provenance

This version was published by a different npm account than previous versions on 2026-04-01. 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.20.0

2 findings
HIGH Publisher changed: ad.vl → mariadias143 (on 2026-03-26) provenance

This version was published by a different npm account than previous versions on 2026-03-26. 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.17.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.17.0

1 finding
LOW No provenance attestation provenance

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

v0.16.0

1 finding
LOW No provenance attestation provenance

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

v0.15.1

1 finding
LOW No provenance attestation provenance

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

v0.15.0

2 findings
HIGH Publisher changed: ad.vl → jmuzina (on 2026-02-20) provenance

This version was published by a different npm account than previous versions on 2026-02-20. 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.11.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.