@mondaydotcomorg/monday-api-queue-sdk
A module for executing / consuming monday.com API requests at scale.
Supply chain provenance
Status for the latest visible version.
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
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): Large monday.com internal org; mass maintainer additions reflect org-wide team management, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added; consistent with internal team rotation at monday.com org. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the initial published version of an official monday.com org package with 14 versions in registry; not a throwaway. | ai | |
| dependencies | unvetted-dep:monday-sdk-js | AI (dependencies): Official monday.com JS SDK; expected dependency for this org's package. | ai | |
| dependencies | unvetted-dep:sqs-consumer | AI (dependencies): Legitimate AWS SQS consumer library; expected dependency for this SDK's queue functionality. | ai | |
| provenance | no-provenance | AI (provenance): Official monday.com org package; absence of Sigstore attestation is common and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:aws-sdk | AI (phantom-deps): aws-sdk is declared as a runtime dep and referenced in config; phantom-dep heuristic misfires here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.1.23 | 9 / 15 | |
| 0.1.22 | 9 / 15 | |
| 0.1.21 | 9 / 15 | |
| 0.1.20 | 9 / 15 | |
| 0.1.19 | 9 / 15 | |
| 0.1.18 | 9 / 15 | |
| 0.1.17 | 9 / 15 | |
| 0.1.16 | 9 / 15 | |
| 0.1.15 | 9 / 15 | |
| 0.1.14 | 9 / 15 | |
| 0.1.13 | 9 / 15 | |
| 0.1.12 | 9 / 15 | |
| 0.1.11 | 9 / 15 | |
| 0.1.10 | 9 / 15 | |
| 0.1.9 | 9 / 15 | |
| 0.1.8 | 9 / 15 | |
| 0.1.7 | 9 / 15 | |
| 0.1.6 | 9 / 15 | |
| 0.1.5 | 9 / 15 | |
| 0.1.4 | 9 / 15 | |
| 0.0.0 | 8 / 13 |
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.