@shun-js/aibaiban-server
aibaiban.com server
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Common for this publisher's packages; no other risk signals present. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is declared and used via config/schema tooling in this package; not a true phantom dep. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): zod-to-json-schema used indirectly via schema config; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:qiao-z-sms | AI (dependencies): Same author ecosystem; stable pattern. | ai | |
| dependencies | unvetted-dep:qiao-z-nuser | AI (dependencies): Same author ecosystem; stable pattern. | ai | |
| dependencies | unvetted-dep:qiao-z | AI (dependencies): Same author ecosystem (uikoo9/shun-js); stable pattern across versions. | ai | |
| dependencies | unvetted-dep:qiao-rate-limit | AI (dependencies): Same author ecosystem; stable pattern. | ai | |
| dependencies | unvetted-dep:qiao-z-service | AI (dependencies): Same author ecosystem; stable pattern. | ai | |
| dependencies | unvetted-dep:qiao-log | AI (dependencies): Same author ecosystem; stable pattern. | ai | |
| dependencies | unvetted-dep:qiao-redis | AI (dependencies): Same author ecosystem; stable pattern. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 1.6.2 | 15 / 0 | |
| 1.6.1 | 15 / 0 | |
| 1.5.4 | 15 / 0 | |
| 1.5.0 | 15 / 0 | |
| 1.4.7 | 15 / 0 | |
| 1.4.6 | 15 / 0 | |
| 1.4.1 | 14 / 0 | |
| 1.4.0 | 14 / 0 | |
| 1.3.9 | 14 / 0 | |
| 1.3.8 | 14 / 0 | |
| 1.3.7 | 14 / 0 | |
| 1.3.6 | 14 / 0 | |
| 1.3.5 | 14 / 0 | |
| 1.3.4 | 14 / 0 | |
| 1.3.3 | 14 / 0 | |
| 1.3.2 | 14 / 0 | |
| 1.3.1 | 14 / 0 | |
| 1.3.0 | 14 / 0 | |
| 1.2.9 | 14 / 0 | |
| 1.2.8 | 14 / 0 | |
| 1.2.7 | 14 / 0 | |
| 1.2.6 | 14 / 0 | |
| 1.2.5 | 14 / 0 | |
| 1.2.4 | 14 / 0 | |
| 1.2.2 | 14 / 0 | |
| 1.2.1 | 14 / 0 | |
| 1.2.0 | 14 / 0 | |
| 1.1.9 | 14 / 0 | |
| 1.1.8 | 14 / 0 | |
| 1.1.7 | 14 / 0 | |
| 1.1.6 | 14 / 0 | |
| 1.1.5 | 14 / 0 | |
| 1.1.4 | 14 / 0 | |
| 1.1.3 | 14 / 0 | |
| 1.1.2 | 14 / 0 | |
| 1.1.1 | 14 / 0 | |
| 1.0.9 | 13 / 0 | |
| 1.0.8 | 13 / 0 | |
| 1.0.7 | 13 / 0 | |
| 1.0.6 | 13 / 0 | |
| 1.0.5 | 13 / 0 | |
| 1.0.4 | 13 / 0 | |
| 1.0.3 | 13 / 0 | |
| 1.0.2 | 13 / 0 | |
| 1.0.1 | 13 / 0 | |
| 1.0.0 | 13 / 0 | |
| 0.9.1 | 13 / 0 | |
| 0.9.0 | 13 / 0 | |
| 0.8.10 | 13 / 0 | |
| 0.8.9 | 13 / 0 | |
| 0.8.8 | 13 / 0 |
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
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.