@constructive-io/node
Constructive SDK for Node.js - Drop-in replacement for @constructive-io/sdk with Node.js HTTP adapter
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @constructive-io/node; Levenshtein match to 'zod' is spurious, no impersonation intent. | ai |
Versions (showing 51 of 82)
| Version | Deps | Published |
|---|---|---|
| 0.10.12 | 2 / 3 | |
| 0.10.11 | 2 / 3 | |
| 0.10.10 | 2 / 3 | |
| 0.10.9 | 2 / 3 | |
| 0.10.8 | 2 / 3 | |
| 0.10.7 | 2 / 3 | |
| 0.10.6 | 2 / 3 | |
| 0.10.5 | 2 / 3 | |
| 0.10.4 | 2 / 3 | |
| 0.10.3 | 2 / 3 | |
| 0.10.2 | 2 / 3 | |
| 0.10.1 | 2 / 3 | |
| 0.10.0 | 2 / 3 | |
| 0.9.4 | 2 / 3 | |
| 0.9.3 | 2 / 3 | |
| 0.9.2 | 2 / 3 | |
| 0.9.1 | 2 / 3 | |
| 0.9.0 | 2 / 3 | |
| 0.8.23 | 2 / 3 | |
| 0.8.22 | 2 / 3 | |
| 0.8.21 | 2 / 3 | |
| 0.8.20 | 2 / 3 | |
| 0.8.19 | 2 / 3 | |
| 0.8.18 | 2 / 3 | |
| 0.8.17 | 2 / 3 | |
| 0.8.16 | 2 / 3 | |
| 0.8.15 | 2 / 3 | |
| 0.8.14 | 2 / 3 | |
| 0.8.13 | 2 / 3 | |
| 0.8.12 | 2 / 3 | |
| 0.8.11 | 2 / 3 | |
| 0.8.10 | 2 / 3 | |
| 0.8.9 | 2 / 3 | |
| 0.8.8 | 2 / 3 | |
| 0.8.7 | 2 / 3 | |
| 0.8.6 | 2 / 3 | |
| 0.8.5 | 2 / 3 | |
| 0.8.4 | 2 / 3 | |
| 0.8.3 | 2 / 3 | |
| 0.8.1 | 2 / 3 | |
| 0.8.0 | 2 / 3 | |
| 0.7.8 | 2 / 3 | |
| 0.7.7 | 2 / 3 | |
| 0.7.6 | 2 / 3 | |
| 0.7.5 | 2 / 3 | |
| 0.7.2 | 2 / 3 | |
| 0.7.1 | 2 / 3 | |
| 0.7.0 | 2 / 3 | |
| 0.6.5 | 2 / 3 | |
| 0.6.4 | 2 / 3 | |
| 0.6.3 | 2 / 3 |
v0.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.