@mondaydotcomorg/agent-toolkit
monday.com agent toolkit
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:unpdf | AI (phantom-deps): Optional document-processing dep; likely dynamically required at runtime, not a direct import. | ai | |
| phantom-deps | phantom-dep:exceljs | AI (phantom-deps): Optional spreadsheet dep; consistent with dynamic/conditional import pattern in this toolkit. | ai | |
| phantom-deps | phantom-dep:mammoth | AI (phantom-deps): Optional document-processing dep; consistent with dynamic/conditional import pattern in this toolkit. | ai |
Versions (showing 36 of 136)
| Version | Deps | Published |
|---|---|---|
| 2.36.1 | 5 / 19 | |
| 2.36.0 | 5 / 19 | |
| 2.35.0 | 5 / 19 | |
| 2.34.0 | 5 / 19 | |
| 2.33.0 | 5 / 19 | |
| 2.32.2 | 5 / 19 | |
| 2.32.1 | 5 / 19 | |
| 2.32.0 | 5 / 19 | |
| 2.31.0 | 5 / 19 | |
| 2.30.0 | 5 / 19 | |
| 2.29.15 | 5 / 19 | |
| 2.29.14 | 5 / 19 | |
| 2.29.12 | 5 / 19 | |
| 2.29.11 | 5 / 19 | |
| 2.29.10 | 5 / 19 | |
| 2.29.9 | 5 / 19 | |
| 2.29.8 | 5 / 19 | |
| 2.29.7 | 5 / 19 | |
| 2.29.6 | 5 / 19 | |
| 2.29.5 | 5 / 19 | |
| 2.29.4 | 5 / 19 | |
| 2.29.3 | 5 / 19 | |
| 2.29.2 | 5 / 19 | |
| 2.29.1 | 5 / 19 | |
| 2.29.0 | 5 / 19 | |
| 2.28.2 | 5 / 19 | |
| 2.28.1 | 5 / 19 | |
| 2.28.0 | 5 / 19 | |
| 2.27.0 | 5 / 19 | |
| 2.26.0 | 5 / 19 | |
| 2.25.0 | 5 / 19 | |
| 2.24.3 | 5 / 19 | |
| 2.24.2 | 5 / 19 | |
| 2.24.1 | 5 / 19 | |
| 2.24.0 | 5 / 19 | |
| 2.23.1 | 5 / 19 |
v2.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.