@edirect/dynamics
Microsoft Dynamics 365 integration module for eDirect NestJS applications. Handles OAuth2 token acquisition (password grant and client credentials), automatic token refresh, and provides `get`, `post`, and `patch` methods for Dynamics API calls.
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
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 11.0.61 | 6 / 4 | |
| 11.0.60 | 6 / 4 | |
| 11.0.59 | 6 / 4 | |
| 11.0.58 | 6 / 4 | |
| 11.0.56 | 6 / 4 | |
| 11.0.55 | 6 / 4 | |
| 11.0.54 | 6 / 4 | |
| 11.0.53 | 6 / 4 | |
| 11.0.52 | 6 / 4 | |
| 11.0.49 | 6 / 4 | |
| 11.0.48 | 6 / 4 | |
| 11.0.43 | 6 / 4 | |
| 11.0.41 | 6 / 4 | |
| 11.0.40 | 6 / 4 | |
| 11.0.39 | 6 / 4 | |
| 11.0.37 | 6 / 4 | |
| 11.0.36 | 6 / 4 | |
| 11.0.35 | 6 / 4 | |
| 11.0.34 | 6 / 4 | |
| 11.0.33 | 6 / 4 | |
| 11.0.30 | 6 / 4 | |
| 11.0.25 | 6 / 4 | |
| 11.0.24 | 6 / 4 |
v11.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.60
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (edirectamorim) than the most recent previously approved version (iquirino.bolttech) on 2026-05-12, but edirectamorim 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.
v11.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.