@ibiz-template/model-helper
模型辅助库
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ibiz-template/core | AI (dependencies): First-party sibling package within same org/monorepo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Sibling dep addition consistent with monorepo pattern, not third-party supply chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Established org package with 320 versions; no provenance is consistent across the entire @ibiz-template scope. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.7.40 | 5 / 3 | |
| 0.7.39 | 5 / 3 | |
| 0.7.34 | 4 / 3 | |
| 0.7.30 | 4 / 3 | |
| 0.7.29 | 4 / 3 | |
| 0.7.28 | 4 / 3 | |
| 0.7.27 | 4 / 3 | |
| 0.7.26 | 4 / 3 | |
| 0.7.25 | 4 / 3 | |
| 0.7.24 | 4 / 3 | |
| 0.7.23 | 4 / 3 | |
| 0.7.22 | 4 / 3 | |
| 0.7.21 | 4 / 3 | |
| 0.7.20 | 4 / 3 | |
| 0.7.19 | 4 / 3 | |
| 0.7.18 | 4 / 3 | |
| 0.7.17 | 4 / 3 | |
| 0.7.16 | 4 / 3 | |
| 0.7.15 | 4 / 3 | |
| 0.7.14 | 4 / 3 | |
| 0.7.13 | 4 / 3 | |
| 0.7.12 | 4 / 3 | |
| 0.7.11 | 4 / 3 | |
| 0.7.10 | 4 / 3 | |
| 0.7.9 | 4 / 3 |
v0.7.39
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zhangpingchuan) than the most recent previously approved version (lengyuace) on 2025-03-31, but zhangpingchuan 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.
v0.7.34
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lengyuace) than the most recent previously approved version (zhangpingchuan) on 2024-07-25, but lengyuace 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.
v0.7.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.