@zenstackhq/sdk
Utilities for building ZenStack plugins
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; expected for this org going forward. | ai | |
| dependencies | unvetted-dep:@prisma/internals-v7 | AI (dependencies): npm alias for @prisma/internals@7; standard dual-version support pattern for this SDK. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal SDK sub-package in the ZenStack monorepo; sparse README/metadata is expected and stable across versions. | ai | |
| dependencies | unvetted-dep:@zenstackhq/runtime | AI (dependencies): Same-org sibling package pinned to matching version; not an external unvetted dependency. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Hardcoded path to @prisma/client/package.json for version detection; not arbitrary module loading. | ai | |
| provenance | no-provenance | AI (provenance): Established ZenStack monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 3.7.2 | 5 / 6 | |
| 3.7.1 | 5 / 6 | |
| 3.7.0 | 5 / 6 | |
| 3.6.4 | 5 / 6 | |
| 3.6.3 | 5 / 6 | |
| 3.6.2 | 5 / 6 | |
| 3.6.1 | 5 / 6 | |
| 3.6.0 | 5 / 6 | |
| 3.5.6 | 5 / 4 | |
| 3.5.5 | 5 / 4 | |
| 3.5.4 | 5 / 4 | |
| 3.5.3 | 5 / 4 | |
| 3.5.2 | 5 / 4 | |
| 3.5.1 | 5 / 4 | |
| 3.5.0 | 5 / 4 | |
| 3.4.6 | 5 / 4 | |
| 3.4.5 | 5 / 4 | |
| 3.4.4 | 5 / 4 | |
| 3.4.3 | 5 / 4 | |
| 3.4.2 | 5 / 4 | |
| 3.4.1 | 5 / 4 | |
| 3.4.0 | 5 / 4 | |
| 3.3.3 | 5 / 4 | |
| 3.3.2 | 5 / 4 | |
| 3.3.1 | 5 / 4 | |
| 3.3.0 | 5 / 4 | |
| 3.2.1 | 5 / 4 | |
| 3.2.0 | 5 / 4 | |
| 3.1.1 | 5 / 4 | |
| 3.1.0 | 5 / 4 | |
| 3.0.0 | 5 / 4 | |
| 2.22.3 | 9 / 1 | |
| 2.22.2 | 9 / 1 | |
| 2.22.1 | 8 / 1 | |
| 2.22.0 | 8 / 1 | |
| 2.21.1 | 8 / 1 | |
| 2.21.0 | 8 / 1 |
v3.7.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-31. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.