← Home

@fiscozen/dialog

npm
8
Versions
—
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

panicofralen_fiscozentrebhcbfiscozenfrancivagosergioterrasifiscozen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): New publisher has strong approval track record (71/0); consistent with org maintainer rotation. ai
phantom-deps phantom-dep:@fiscozen/style AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo design system components. ai
phantom-deps phantom-dep:@fiscozen/composables AI (phantom-deps): Same-org scoped package; stable false positive for this design system. ai
phantom-deps phantom-dep:dialog-polyfill AI (phantom-deps): Referenced in config files per analyzer note; not a real phantom dep concern. ai

Versions (showing 8 of 8)

Version Deps Published
0.1.31 4 / 20
0.1.30 4 / 20
0.1.29 4 / 20
0.1.28 4 / 20
0.1.27 4 / 20
0.1.26 4 / 20
0.1.25 2 / 20
0.1.24 2 / 20

v0.1.31

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

2 findings
HIGH Publisher changed: trebh → sergioterrasifiscozen (on 2026-03-09) provenance

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

2 findings
HIGH Publisher changed: trebh → sergioterrasifiscozen (on 2026-03-03) provenance

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

2 findings
HIGH Publisher changed: trebh → sergioterrasifiscozen (on 2026-03-02) provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.1.25

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

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.