← Home

@fiscozen/dialog

npm
35
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, so a manually published version cannot be tied back to a reviewed commit.

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 35 of 35)

Version Deps Published
0.1.34 4 / 20
0.1.33 4 / 20
0.1.32 4 / 20
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
0.1.23 2 / 20
0.1.22 2 / 20
0.1.21 2 / 20
0.1.20 2 / 20
0.1.19 2 / 20
0.1.18 1 / 20
0.1.17 1 / 20
0.1.16 1 / 20
0.1.15 1 / 20
0.1.14 1 / 20
0.1.13 1 / 20
0.1.12 1 / 20
0.1.11 1 / 20
0.1.10 1 / 20
0.1.9 0 / 20
0.1.8 0 / 20
0.1.7 0 / 20
0.1.6 0 / 20
0.1.5 0 / 20
0.1.4 0 / 20
0.1.3 0 / 20
0.1.2 0 / 20
0.1.1 0 / 20
0.1.0 0 / 20

v0.1.23

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: trebh → alen_fiscozen (on 2024-11-28, known maintainer) provenance

This version was published by a different npm account (alen_fiscozen) than the most recent previously approved version (trebh) on 2024-11-28, but alen_fiscozen 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.22

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: alen_fiscozen → trebh (on 2024-11-19, known maintainer) provenance

This version was published by a different npm account (trebh) than the most recent previously approved version (alen_fiscozen) on 2024-11-19, but trebh 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.21

1 finding
LOW No provenance attestation provenance

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

v0.1.20

1 finding
LOW No provenance attestation provenance

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

v0.1.19

1 finding
LOW No provenance attestation provenance

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

v0.1.18

1 finding
LOW No provenance attestation provenance

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

v0.1.17

1 finding
LOW No provenance attestation provenance

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

v0.1.16

1 finding
LOW No provenance attestation provenance

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

v0.1.15

1 finding
LOW No provenance attestation provenance

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

v0.1.14

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: cbfiscozen → alen_fiscozen (on 2024-10-17, known maintainer) provenance

This version was published by a different npm account (alen_fiscozen) than the most recent previously approved version (cbfiscozen) on 2024-10-17, but alen_fiscozen 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.13

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: cbfiscozen → alen_fiscozen (on 2024-09-11, known maintainer) provenance

This version was published by a different npm account (alen_fiscozen) than the most recent previously approved version (cbfiscozen) on 2024-09-11, but alen_fiscozen 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.12

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: trebh → cbfiscozen (on 2024-09-11, known maintainer) provenance

This version was published by a different npm account (cbfiscozen) than the most recent previously approved version (trebh) on 2024-09-11, but cbfiscozen 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.11

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: alen_fiscozen → trebh (on 2024-08-14, known maintainer) provenance

This version was published by a different npm account (trebh) than the most recent previously approved version (alen_fiscozen) on 2024-08-14, but trebh 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.10

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: trebh → alen_fiscozen (on 2024-08-06, known maintainer) provenance

This version was published by a different npm account (alen_fiscozen) than the most recent previously approved version (trebh) on 2024-08-06, but alen_fiscozen 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.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

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: trebh → alen_fiscozen (on 2024-07-31, known maintainer) provenance

This version was published by a different npm account (alen_fiscozen) than the most recent previously approved version (trebh) on 2024-07-31, but alen_fiscozen 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.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.