unctx
Composition-api in Vanilla js
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Build-env change on trusted unjs package; not a malicious signal. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Diff baseline (v0.0.3) is far older than last real release; not true dormancy. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deps support new transform/plugin exports, legitimate AST tooling. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Growth matches new transform/plugin feature set, not injected payload. | ai | |
| bogus-package | bogus-package | AI (bogus-package): pi0/unjs ecosystem package; antfu co-maintainer flag is a false positive, inflated semver reflects a registry migration of a mature library, not a new spam package. | ai | |
| provenance | no-provenance | AI (provenance): Trusted publisher (pi0/unjs org) with strong track record; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 14 | |
| 2.5.0 | 4 / 11 | |
| 2.4.1 | 4 / 11 | |
| 2.4.0 | 4 / 11 | |
| 2.3.1 | 4 / 11 | |
| 2.3.0 | 4 / 11 | |
| 2.2.0 | 4 / 11 | |
| 2.1.2 | 4 / 11 | |
| 2.1.1 | 4 / 11 | |
| 2.1.0 | 4 / 11 | |
| 2.0.2 | 4 / 12 | |
| 2.0.1 | 4 / 11 | |
| 2.0.0 | 4 / 11 | |
| 0.0.3 | 0 / 9 |
v3.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pi0.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pi0.
v2.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pi0.
v2.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pi0.
v2.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pi0.
v2.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pi0.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.