@zenstackhq/server
ZenStack automatic CRUD API handlers and server adapters for popular frameworks
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 used for Prisma Bytes serialization/deserialization; not obfuscation or payload hiding. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped package in established ZenStack monorepo; not a typosquat of semver. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.7.1 | 9 / 21 | |
| 3.7.0 | 9 / 21 | |
| 3.6.4 | 9 / 21 | |
| 3.6.3 | 9 / 21 | |
| 3.6.2 | 9 / 21 | |
| 3.6.1 | 9 / 21 | |
| 3.6.0 | 9 / 21 | |
| 3.5.6 | 9 / 20 | |
| 3.5.5 | 9 / 20 | |
| 3.5.4 | 9 / 20 | |
| 3.5.3 | 9 / 20 | |
| 3.5.2 | 9 / 20 | |
| 3.5.1 | 9 / 20 | |
| 3.5.0 | 9 / 20 | |
| 3.4.6 | 8 / 19 | |
| 3.4.5 | 8 / 19 | |
| 3.4.4 | 8 / 19 | |
| 3.4.3 | 8 / 19 | |
| 3.4.2 | 8 / 19 | |
| 3.4.1 | 8 / 19 | |
| 3.4.0 | 8 / 19 | |
| 3.3.3 | 8 / 19 | |
| 3.3.2 | 8 / 19 | |
| 3.3.1 | 8 / 19 | |
| 3.3.0 | 8 / 19 | |
| 3.2.1 | 8 / 19 | |
| 3.2.0 | 8 / 19 | |
| 3.1.1 | 8 / 19 | |
| 3.1.0 | 8 / 19 | |
| 3.0.0 | 8 / 19 | |
| 2.22.3 | 5 / 21 | |
| 2.22.1 | 5 / 21 | |
| 2.21.1 | 5 / 21 | |
| 2.21.0 | 5 / 21 |
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.