react-big-calendar No license 75 versions

react-big-calendar

npm Repository Homepage

75

Versions

—

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

Maintainers

monastic.panictobiasandersencutterbl

Keywords

schedulerreact-componentreactcalendareventsfull calendar

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Long-tenured publisher (1269d), 49 approved packages, no takeover pattern.	ai	2026/07/25
provenance	publisher-changed-stale	AI (provenance): Stable for 1269d on npm; consistent with legitimate maintainer transfer.	ai	2026/07/25
dependencies	unvetted-dep:globalize	AI (dependencies): Long-standing optional localizer dep in this package; stable false positive.	ai	2026/05/18
dependencies	unvetted-dep:react-overlays	AI (dependencies): Core UI dep used for popup/overlay positioning; stable for this package.	ai	2026/05/18
phantom-deps	phantom-dep:luxon	AI (phantom-deps): luxon is an optional localizer; declared as dep for consumers who use it, not directly imported in core.	ai	2026/05/18
phantom-deps	phantom-dep:moment-timezone	AI (phantom-deps): moment-timezone is an optional localizer dependency; same pattern.	ai	2026/05/18
phantom-deps	phantom-dep:moment	AI (phantom-deps): moment is an optional localizer; same pattern as luxon.	ai	2026/05/18
phantom-deps	phantom-dep:globalize	AI (phantom-deps): globalize is an optional localizer; same pattern.	ai	2026/05/18
phantom-deps	phantom-dep:lodash-es	AI (phantom-deps): lodash-es is a declared dep used in ESM build; phantom-dep heuristic false positive.	ai	2026/05/18

Versions (showing 75 of 75)

Version	Deps	Published
1.20.0	16 / 62	2026-06-01
1.19.6	16 / 59	2026-05-29
1.19.4	16 / 59	2025-06-16
1.19.3	16 / 59	2025-06-12
1.19.2	16 / 59	2025-05-28
1.19.1	16 / 59	2025-05-28
1.19.0	16 / 59	2025-05-28
1.18.0	16 / 59	2025-02-24
1.17.1	16 / 59	2024-12-19
1.17.0	16 / 59	2024-12-11
1.16.3	16 / 59	2024-11-26
1.16.2	16 / 59	2024-11-25
1.16.1	16 / 59	2024-11-25
1.16.0	16 / 59	2024-11-21
1.15.0	16 / 59	2024-10-01
1.14.1	16 / 59	2024-09-16
1.14.0	16 / 59	2024-09-12
1.13.4	16 / 59	2024-08-23
1.13.3	16 / 59	2024-08-19
1.13.2	16 / 59	2024-08-06
1.13.1	16 / 59	2024-07-12
1.13.0	16 / 59	2024-06-11
1.12.2	16 / 59	2024-05-14
1.12.1	16 / 59	2024-04-30
1.12.0	16 / 59	2024-04-25
1.11.7	16 / 59	2024-04-25
1.11.6	16 / 59	2024-04-15
1.11.5	16 / 59	2024-04-15
1.11.4	16 / 59	2024-04-15
1.11.3	16 / 59	2024-04-02
1.11.2	16 / 59	2024-03-12
1.11.1	16 / 59	2024-03-04
1.11.0	16 / 59	2024-02-26
1.10.3	16 / 59	2024-02-21
1.10.2	16 / 59	2024-02-19
1.10.1	16 / 59	2024-02-14
1.10.0	16 / 59	2024-02-09
1.9.2	16 / 59	2024-02-09
1.9.1	16 / 59	2024-02-07
1.9.0	16 / 59	2024-02-07
1.8.7	16 / 59	2024-01-26
1.8.6	16 / 59	2024-01-08
1.8.5	16 / 59	2023-10-30
1.8.4	16 / 59	2023-09-18
1.8.3	16 / 59	2023-09-18
1.8.2	16 / 57	2023-08-07
1.8.1	16 / 57	2023-06-05
1.8.0	16 / 57	2023-06-02
1.7.0	16 / 57	2023-06-02
1.6.9	16 / 57	2023-03-24
1.6.8	16 / 57	2023-02-17
1.6.7	16 / 57	2023-02-15
1.6.6	16 / 57	2023-02-15
1.6.5	16 / 57	2023-02-14
1.6.4	16 / 57	2023-02-09
1.6.3	16 / 57	2023-02-01
1.5.2	15 / 57	2022-11-10
1.5.1	15 / 57	2022-11-09
1.5.0	15 / 57	2022-07-19
1.4.3	15 / 57	2022-07-19
1.4.2	15 / 57	2022-07-15
1.4.1	15 / 57	2022-07-15
1.4.0	15 / 57	2022-07-12
1.3.3	15 / 57	2022-07-12
1.3.2	15 / 57	2022-07-12
1.3.1	15 / 57	2022-07-12
1.3.0	15 / 57	2022-07-11
1.2.4	15 / 57	2022-07-11
1.2.3	15 / 57	2022-07-11
1.2.2	15 / 57	2022-07-11
1.2.1	15 / 57	2022-07-08
1.2.0	15 / 57	2022-07-08
1.1.0	15 / 57	2022-07-08
1.0.1	15 / 61	2022-07-07
1.0.0	15 / 61	2022-07-07

v1.20.0

1 finding

LOW No provenance attestation provenance

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

v1.19.6

1 finding

LOW No provenance attestation provenance

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

v1.18.0

1 finding

LOW No provenance attestation provenance

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

v1.17.1

1 finding

LOW No provenance attestation provenance

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

v1.17.0

1 finding

LOW No provenance attestation provenance

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

v1.16.3

1 finding

LOW No provenance attestation provenance

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

v1.16.2

1 finding

LOW No provenance attestation provenance

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

v1.16.1

1 finding

LOW No provenance attestation provenance

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

v1.16.0

1 finding

LOW No provenance attestation provenance

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

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.1

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.4

1 finding

LOW No provenance attestation provenance

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

v1.13.3

1 finding

LOW No provenance attestation provenance

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

v1.13.2

1 finding

LOW No provenance attestation provenance

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

v1.13.1

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.2

1 finding

LOW No provenance attestation provenance

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

v1.12.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.

v1.12.0

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-04-25, unremoved on npm for 820d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-04-25. It has since remained available on npm for 820 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.7

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-04-25, unremoved on npm for 820d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-04-25. It has since remained available on npm for 820 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.6

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-04-15, unremoved on npm for 830d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-04-15. It has since remained available on npm for 830 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.5

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-04-15, unremoved on npm for 830d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-04-15. It has since remained available on npm for 830 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.4

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-04-15, unremoved on npm for 830d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-04-15. It has since remained available on npm for 830 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.3

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-04-02, unremoved on npm for 843d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-04-02. It has since remained available on npm for 843 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.2

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-03-12, unremoved on npm for 864d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-03-12. It has since remained available on npm for 864 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.1

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-03-04, unremoved on npm for 872d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-03-04. It has since remained available on npm for 872 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.0

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-02-26, unremoved on npm for 879d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-02-26. It has since remained available on npm for 879 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.10.3

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-02-21, unremoved on npm for 884d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-02-21. It has since remained available on npm for 884 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.10.2

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-02-19, unremoved on npm for 886d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-02-19. It has since remained available on npm for 886 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.10.1

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-02-14, unremoved on npm for 891d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-02-14. It has since remained available on npm for 891 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.10.0

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-02-09, unremoved on npm for 896d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-02-09. It has since remained available on npm for 896 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.9.2

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-02-09, unremoved on npm for 896d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-02-09. It has since remained available on npm for 896 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.9.1

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-02-07, unremoved on npm for 898d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-02-07. It has since remained available on npm for 898 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.9.0

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-02-07, unremoved on npm for 898d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-02-07. It has since remained available on npm for 898 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.8.7

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-01-26, unremoved on npm for 910d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-01-26. It has since remained available on npm for 910 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.8.6

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2024-01-08, unremoved on npm for 928d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2024-01-08. It has since remained available on npm for 928 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.8.5

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-10-30, unremoved on npm for 998d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-10-30. It has since remained available on npm for 998 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.8.4

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-09-18, unremoved on npm for 1040d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-09-18. It has since remained available on npm for 1040 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.8.3

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-09-18, unremoved on npm for 1040d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-09-18. It has since remained available on npm for 1040 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.8.2

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-08-07, unremoved on npm for 1082d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-08-07. It has since remained available on npm for 1082 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.8.1

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-06-05, unremoved on npm for 1145d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-06-05. It has since remained available on npm for 1145 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.8.0

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-06-02, unremoved on npm for 1148d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-06-02. It has since remained available on npm for 1148 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.7.0

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-06-02, unremoved on npm for 1148d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-06-02. It has since remained available on npm for 1148 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.6.9

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-03-24, unremoved on npm for 1218d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-03-24. It has since remained available on npm for 1218 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.6.8

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-02-17, unremoved on npm for 1253d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-02-17. It has since remained available on npm for 1253 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.6.7

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-02-15, unremoved on npm for 1255d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-02-15. It has since remained available on npm for 1255 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.6.6

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-02-15, unremoved on npm for 1255d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-02-15. It has since remained available on npm for 1255 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.6.5

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-02-14, unremoved on npm for 1256d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-02-14. It has since remained available on npm for 1256 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.6.4

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-02-09, unremoved on npm for 1261d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-02-09. It has since remained available on npm for 1261 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.6.3

2 findings

MEDIUM Publisher changed: monastic.panic → cutterbl (on 2023-02-01, unremoved on npm for 1269d) provenance

This version was published by a different npm account (cutterbl) than the most recent previously approved version (monastic.panic) on 2023-02-01. It has since remained available on npm for 1269 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.5.1

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.3

1 finding

LOW No provenance attestation provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

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