@sapphire/async-queue — Greenflagged

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

favnavladfrangukyranet

Keywords

@sapphire/async-queuebottypescripttsyarndiscordsapphirestandalone

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): Same publisher favna; cosmetic name variance, not a real maintainer change.	ai	2026/07/19
maintainer-change	maintainer-removed	AI (maintainer-change): Same publisher favna; cosmetic name variance, not a real maintainer change.	ai	2026/07/19
provenance	publisher-changed-stale	AI (provenance): Long-stable publish (1749d) rules out takeover; same account.	ai	2026/07/19

Versions (showing 29 of 29)

Version	Deps	Published
1.5.5	0 / 8	2024-11-09
1.5.4	0 / 8	2024-11-02
1.5.3	0 / 8	2024-07-23
1.5.2	0 / 7	2024-01-19
1.5.1	0 / 7	2023-12-04
1.5.0	0 / 6	2022-08-16
1.4.0	0 / 3	2022-08-07
1.3.2	0 / 2	2022-06-26
1.3.1	0 / 0	2022-04-01
1.3.0	0 / 0	2022-03-06
1.2.0	0 / 0	2022-01-28
1.1.9	0 / 0	2021-11-06
1.1.8	0 / 0	2021-10-26
1.1.7	0 / 0	2021-10-17
1.1.6	0 / 0	2021-10-11
1.1.5	0 / 0	2021-10-04
1.1.4	0 / 0	2021-06-27
1.1.3	0 / 0	2021-06-06
1.1.2	0 / 0	2021-05-20
1.1.1	0 / 0	2021-05-02
1.1.0	0 / 0	2021-04-21
1.0.7	0 / 0	2021-04-19
1.0.6	0 / 0	2021-04-03
1.0.5	0 / 0	2021-03-16
1.0.4	0 / 0	2021-02-16
1.0.3	0 / 0	2021-02-13
1.0.2	0 / 0	2021-01-25
1.0.1	0 / 0	2021-01-16
1.0.0	0 / 0	2021-01-13

v1.5.4

1 finding

LOW No provenance attestation provenance

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

v1.5.3

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

2 findings

MEDIUM Publisher changed: favna. → favna (on 2024-01-19, unremoved on npm for 912d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2024-01-19. It has since remained available on npm for 912 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.1

2 findings

MEDIUM Publisher changed: favna. → favna (on 2023-12-04, unremoved on npm for 958d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2023-12-04. It has since remained available on npm for 958 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.0

2 findings

MEDIUM Publisher changed: favna. → favna (on 2022-08-16, unremoved on npm for 1433d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2022-08-16. It has since remained available on npm for 1433 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.4.0

2 findings

MEDIUM Publisher changed: favna. → favna (on 2022-08-07, unremoved on npm for 1442d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2022-08-07. It has since remained available on npm for 1442 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.3.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: favna. → vladfrangu (on 2022-06-26, known maintainer) provenance

This version was published by a different npm account (vladfrangu) than the most recent previously approved version (favna.) on 2022-06-26, but vladfrangu 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.

v1.3.1

2 findings

MEDIUM Publisher changed: favna. → favna (on 2022-04-01, unremoved on npm for 1570d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2022-04-01. It has since remained available on npm for 1570 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.3.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: favna. → vladfrangu (on 2022-03-06, known maintainer) provenance

This version was published by a different npm account (vladfrangu) than the most recent previously approved version (favna.) on 2022-03-06, but vladfrangu 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.

v1.2.0

2 findings

MEDIUM Publisher changed: favna. → favna (on 2022-01-28, unremoved on npm for 1633d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2022-01-28. It has since remained available on npm for 1633 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.1.9

2 findings

MEDIUM Publisher changed: favna. → favna (on 2021-11-06, unremoved on npm for 1716d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2021-11-06. It has since remained available on npm for 1716 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.1.8

2 findings

MEDIUM Publisher changed: favna. → favna (on 2021-10-26, unremoved on npm for 1727d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2021-10-26. It has since remained available on npm for 1727 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.1.7

2 findings

MEDIUM Publisher changed: favna. → favna (on 2021-10-17, unremoved on npm for 1736d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2021-10-17. It has since remained available on npm for 1736 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.1.6

2 findings

MEDIUM Publisher changed: favna. → favna (on 2021-10-11, unremoved on npm for 1742d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2021-10-11. It has since remained available on npm for 1742 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.1.5

2 findings

MEDIUM Publisher changed: favna. → favna (on 2021-10-04, unremoved on npm for 1749d) provenance

This version was published by a different npm account (favna) than the most recent previously approved version (favna.) on 2021-10-04. It has since remained available on npm for 1749 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.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

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

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

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

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.