@holo-js/adapter-next
Holo-JS Framework - Next.js adapter
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 | no-provenance | AI (provenance): New small framework package; lack of provenance is common and not a risk indicator given no other malicious signals. | ai | |
| dependencies | unvetted-dep:@holo-js/forms | AI (dependencies): workspace:* constraint is an internal monorepo reference resolved at build time; not a runtime npm dependency risk in the published artifact. | ai | |
| dependencies | unvetted-dep:@holo-js/config | AI (dependencies): workspace:* constraint is an internal monorepo reference resolved at build time; not a runtime npm dependency risk in the published artifact. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.3.7 | 3 / 6 | |
| 0.3.6 | 3 / 6 | |
| 0.3.5 | 3 / 6 | |
| 0.3.4 | 3 / 6 | |
| 0.3.3 | 3 / 6 | |
| 0.3.2 | 3 / 6 | |
| 0.3.1 | 3 / 6 | |
| 0.3.0 | 3 / 6 | |
| 0.2.6 | 2 / 6 | |
| 0.2.5 | 2 / 6 | |
| 0.2.4 | 2 / 6 | |
| 0.2.3 | 2 / 6 | |
| 0.2.2 | 2 / 6 | |
| 0.2.1 | 2 / 6 | |
| 0.2.0 | 2 / 6 | |
| 0.1.9 | 2 / 5 | |
| 0.1.8 | 2 / 5 | |
| 0.1.7 | 2 / 5 | |
| 0.1.6 | 2 / 5 | |
| 0.1.5 | 2 / 5 | |
| 0.1.4 | 2 / 4 | |
| 0.1.3 | 2 / 4 | |
| 0.1.2 | 3 / 4 | |
| 0.1.1 | 3 / 4 | |
| 0.1.0 | 3 / 4 |
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.