← Home

@holoscript/holoscript-agent

npm Repository Homepage

Headless agent runtime for the HoloMesh — multi-LLM-provider, brain-mounted, cost-guarded. Closes W.087 vertex B.

29
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

brianonbased

Keywords

holoscriptagentaimcpholomeshteamheadlessruntimemulti-llm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Publisher has strong track record; no behavioral changes; likely a publish environment shift, not malicious. ai

Versions (showing 29 of 29)

Version Deps Published
2.1.22 4 / 4
2.1.21 4 / 4
2.1.20 4 / 4
2.1.19 3 / 4
2.1.18 3 / 4
2.1.17 2 / 4
2.1.16 2 / 4
2.1.15 2 / 4
2.1.14 2 / 4
2.1.13 2 / 4
2.1.12 2 / 4
2.1.11 2 / 4
2.1.10 2 / 4
2.1.9 2 / 4
2.1.8 2 / 4
2.1.7 2 / 4
2.1.6 2 / 4
2.1.5 2 / 4
2.1.4 2 / 4
2.1.3 2 / 4
2.1.2 2 / 4
2.1.1 2 / 4
2.1.0 2 / 4
2.0.7 2 / 4
2.0.4 2 / 4
2.0.3 2 / 4
2.0.2 2 / 4
2.0.1 2 / 4
2.0.0 2 / 4

v2.1.22

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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: brianonbased.

v2.1.21

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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: brianonbased.

v2.1.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.19

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: brianonbased.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.18

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: brianonbased.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.