← Home

@umijs/renderer-react

npm Repository Homepage

@umijs/renderer-react

100
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

sorryccchenshuai2144kuitospeachscriptxiaohuoniyifankakaxixierenyuanxusd320zoomdong07

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Publisher is a known prior maintainer per provenance INFO; not a takeover. ai
maintainer-change maintainer-added AI (maintainer-change): Known maintainer publish, matches umijs org pattern. ai
provenance missing-githead AI (provenance): Minor CI metadata gap for trusted long-running monorepo publisher, no behavioral risk. ai
phantom-deps phantom-dep:@loadable/component AI (phantom-deps): Used via config/build tooling, not a direct import; expected for this package type. ai
phantom-deps phantom-dep:@types/react AI (phantom-deps): Framework-scoped types; stable pattern for React renderer packages. ai
phantom-deps phantom-dep:@types/react-dom AI (phantom-deps): Framework-scoped types; stable pattern for React renderer packages. ai
phantom-deps phantom-dep:@types/react-router-config AI (phantom-deps): Framework-scoped types; stable pattern for React renderer packages. ai
bogus-package bogus-package AI (bogus-package): Minimal README typical of internal monorepo packages; not indicative of spam. ai

Versions (showing 100 of 306)

Hide prereleases
Version Deps Published
3.4.11 5 / 0
3.4.10 5 / 0
3.4.9 5 / 0
3.4.8 5 / 0
3.4.7 5 / 0
3.4.6 5 / 0
3.4.5 5 / 0
3.4.4 5 / 0
3.4.3 5 / 0
3.4.2 5 / 0
3.4.1 5 / 0
3.4.0 5 / 0
3.3.15 5 / 0
3.3.14 5 / 0
3.3.12 5 / 0
3.3.11 5 / 0
3.3.10 5 / 0
3.3.9 5 / 0
3.3.8 5 / 0
3.3.7 5 / 0
3.3.6 5 / 0
3.3.5 7 / 0
3.3.4 7 / 0
3.3.3 7 / 0
3.3.2 7 / 0
3.3.1 7 / 0
3.3.0 7 / 0
3.2.28 7 / 0
3.2.27 7 / 0
3.2.26 7 / 0
3.2.25 7 / 0
3.2.24 7 / 0
3.2.23 7 / 0
3.2.22 7 / 0
3.2.21 7 / 0
3.2.20 7 / 0
3.2.19 7 / 0
3.2.18 7 / 0
3.2.17 7 / 0
3.2.16 7 / 0
3.2.15 7 / 0
3.2.14 7 / 0
3.2.13 7 / 0
3.2.12 7 / 0
3.2.11 7 / 0
3.2.10 7 / 0
3.2.9 7 / 0
3.2.8 7 / 0
3.2.7 7 / 0
3.2.6 7 / 0
3.2.5 7 / 0
3.2.4 7 / 0
3.2.3 7 / 0
3.2.2 7 / 0
3.2.1 7 / 0
3.2.0 7 / 0
3.1.4 7 / 0
3.1.3 7 / 0
3.1.2 7 / 0
3.1.1 7 / 0
3.1.0 7 / 0
3.0.18 7 / 0
3.0.17 7 / 0
3.0.16 7 / 0
3.0.15 7 / 0
3.0.14 7 / 0
3.0.13 7 / 0
3.0.12 7 / 0
3.0.11 7 / 0
3.0.10 7 / 0
3.0.9 7 / 0
3.0.8 7 / 0
3.0.7 7 / 0
3.0.6 7 / 0
3.0.5 7 / 0
3.0.4 7 / 0
3.0.3 7 / 0
3.0.2 7 / 0
3.0.1 7 / 0
3.0.0 7 / 0
4.5.1-canary.20250928.1 5 / 2
4.4.13-canary.20250917.1 5 / 2
4.4.13-canary.20250915.3 5 / 2
4.4.13-canary.20250915.2 5 / 2
4.4.13-canary.20250915.1 5 / 2
4.4.13-canary.20250912.1 5 / 2
4.4.13-canary.20250911.1 5 / 2
4.4.13-canary.20250910.1 5 / 2
4.0.0-canary.20260325.1 5 / 2
4.0.0-canary.20260303.1 5 / 2
4.0.0-canary.20260106.2 5 / 2
4.0.0-canary.20260106.1 5 / 2
4.0.0-canary.20260105.1 5 / 2
4.0.0-canary.20260105.0 5 / 2
4.0.0-canary.20251209.1 5 / 2
4.0.0-canary.20251124.1 5 / 2
4.0.0-canary.20251120.1 5 / 2
4.0.0-canary.20251116.1 5 / 2
4.0.0-canary.20251113.1 5 / 2
4.0.0-canary.20251110.1 5 / 2
Showing 100 of 306 Next page →

v3.4.11

1 finding
LOW No provenance attestation provenance

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

v3.4.10

1 finding
LOW No provenance attestation provenance

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

v3.4.9

1 finding
LOW No provenance attestation provenance

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

v3.4.8

1 finding
LOW No provenance attestation provenance

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

v3.4.7

1 finding
LOW No provenance attestation provenance

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

v3.4.6

1 finding
LOW No provenance attestation provenance

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

v3.4.5

1 finding
LOW No provenance attestation provenance

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

v3.4.4

1 finding
LOW No provenance attestation provenance

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

v3.4.3

1 finding
LOW No provenance attestation provenance

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

v3.4.2

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: ycjcl868 → sorrycc (on 2021-03-12, known maintainer) provenance

This version was published by a different npm account (sorrycc) than the most recent previously approved version (ycjcl868) on 2021-03-12, but sorrycc 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.

v3.4.1

1 finding
LOW No provenance attestation provenance

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

v3.4.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: ycjcl868 → sorrycc (on 2021-03-09, known maintainer) provenance

This version was published by a different npm account (sorrycc) than the most recent previously approved version (ycjcl868) on 2021-03-09, but sorrycc 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.

v3.3.15

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: sorrycc → peachscript (on 2023-05-24, known maintainer) provenance

This version was published by a different npm account (peachscript) than the most recent previously approved version (sorrycc) on 2023-05-24, but peachscript 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.

v3.3.14

1 finding
LOW No provenance attestation provenance

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

v3.3.12

1 finding
LOW No provenance attestation provenance

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

v3.3.11

1 finding
LOW No provenance attestation provenance

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

v3.3.10

1 finding
LOW No provenance attestation provenance

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

v3.3.9

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: sorrycc → ycjcl868 (on 2021-02-23, known maintainer) provenance

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

v3.3.8

1 finding
LOW No provenance attestation provenance

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

v3.3.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: ycjcl868 → sorrycc (on 2021-01-20, known maintainer) provenance

This version was published by a different npm account (sorrycc) than the most recent previously approved version (ycjcl868) on 2021-01-20, but sorrycc 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.

v3.3.6

1 finding
LOW No provenance attestation provenance

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

v3.3.5

1 finding
LOW No provenance attestation provenance

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

v3.3.4

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: ycjcl868 → sorrycc (on 2021-01-08, known maintainer) provenance

This version was published by a different npm account (sorrycc) than the most recent previously approved version (ycjcl868) on 2021-01-08, but sorrycc 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.

v3.3.3

1 finding
LOW No provenance attestation provenance

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

v3.3.2

1 finding
LOW No provenance attestation provenance

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

v3.3.1

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.28

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: sorrycc → ycjcl868 (on 2020-11-20, known maintainer) provenance

This version was published by a different npm account (ycjcl868) than the most recent previously approved version (sorrycc) on 2020-11-20, but ycjcl868 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.

v3.2.27

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: sorrycc → ycjcl868 (on 2020-11-11, known maintainer) provenance

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

v3.2.26

1 finding
LOW No provenance attestation provenance

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

v3.2.25

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: sorrycc → ycjcl868 (on 2020-11-05, known maintainer) provenance

This version was published by a different npm account (ycjcl868) than the most recent previously approved version (sorrycc) on 2020-11-05, but ycjcl868 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.

v3.2.24

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: ycjcl868 → sorrycc (on 2020-10-20, known maintainer) provenance

This version was published by a different npm account (sorrycc) than the most recent previously approved version (ycjcl868) on 2020-10-20, but sorrycc 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.

v3.2.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: sorrycc → ycjcl868 (on 2020-10-09, known maintainer) provenance

This version was published by a different npm account (ycjcl868) than the most recent previously approved version (sorrycc) on 2020-10-09, but ycjcl868 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.

v3.2.22

1 finding
LOW No provenance attestation provenance

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

v3.2.21

1 finding
LOW No provenance attestation provenance

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

v3.2.20

1 finding
LOW No provenance attestation provenance

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

v3.2.19

1 finding
LOW No provenance attestation provenance

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

v3.2.18

1 finding
LOW No provenance attestation provenance

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

v3.2.17

1 finding
LOW No provenance attestation provenance

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

v3.2.16

1 finding
LOW No provenance attestation provenance

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

v3.2.15

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: ycjcl868 → sorrycc (on 2020-08-14, known maintainer) provenance

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

v3.2.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: ycjcl868 → sorrycc (on 2020-07-31, known maintainer) provenance

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

v3.2.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: sorrycc → ycjcl868 (on 2020-07-29, known maintainer) provenance

This version was published by a different npm account (ycjcl868) than the most recent previously approved version (sorrycc) on 2020-07-29, but ycjcl868 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.

v3.2.12

1 finding
LOW No provenance attestation provenance

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

v3.2.11

1 finding
LOW No provenance attestation provenance

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

v3.2.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: sorrycc → ycjcl868 (on 2020-07-15, known maintainer) provenance

This version was published by a different npm account (ycjcl868) than the most recent previously approved version (sorrycc) on 2020-07-15, but ycjcl868 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.

v3.2.9

1 finding
LOW No provenance attestation provenance

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

v3.2.8

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: ycjcl868 → sorrycc (on 2020-07-06, known maintainer) provenance

This version was published by a different npm account (sorrycc) than the most recent previously approved version (ycjcl868) on 2020-07-06, but sorrycc 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.

v3.2.7

1 finding
LOW No provenance attestation provenance

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

v3.2.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: ycjcl868 → sorrycc (on 2020-06-28, known maintainer) provenance

This version was published by a different npm account (sorrycc) than the most recent previously approved version (ycjcl868) on 2020-06-28, but sorrycc 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.

v3.2.5

1 finding
LOW No provenance attestation provenance

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

v3.2.4

1 finding
LOW No provenance attestation provenance

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

v3.2.3

1 finding
LOW No provenance attestation provenance

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

v3.2.2

1 finding
LOW No provenance attestation provenance

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

v3.2.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: sorrycc → ycjcl868 (on 2020-05-19, known maintainer) provenance

This version was published by a different npm account (ycjcl868) than the most recent previously approved version (sorrycc) on 2020-05-19, but ycjcl868 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.

v3.2.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: sorrycc → ycjcl868 (on 2020-05-19, known maintainer) provenance

This version was published by a different npm account (ycjcl868) than the most recent previously approved version (sorrycc) on 2020-05-19, but ycjcl868 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.

v3.1.4

1 finding
LOW No provenance attestation provenance

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

v3.1.3

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: ycjcl868 → sorrycc (on 2020-05-06, known maintainer) provenance

This version was published by a different npm account (sorrycc) than the most recent previously approved version (ycjcl868) on 2020-05-06, but sorrycc 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.

v3.1.2

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: sorrycc → ycjcl868 (on 2020-04-25, known maintainer) provenance

This version was published by a different npm account (ycjcl868) than the most recent previously approved version (sorrycc) on 2020-04-25, but ycjcl868 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.

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.18

1 finding
LOW No provenance attestation provenance

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

v3.0.17

1 finding
LOW No provenance attestation provenance

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

v3.0.16

1 finding
LOW No provenance attestation provenance

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

v3.0.15

1 finding
LOW No provenance attestation provenance

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

v3.0.14

1 finding
LOW No provenance attestation provenance

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

v3.0.13

1 finding
LOW No provenance attestation provenance

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

v3.0.12

1 finding
LOW No provenance attestation provenance

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

v3.0.11

1 finding
LOW No provenance attestation provenance

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

v3.0.10

1 finding
LOW No provenance attestation provenance

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

v3.0.9

1 finding
LOW No provenance attestation provenance

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

v3.0.8

1 finding
LOW No provenance attestation provenance

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

v3.0.7

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.4

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.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.

v3.0.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.