@holoscript/std
HoloScript Standard Library - Core types and utilities
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publisher has strong history; no behavioral evidence of tampering. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Consistent with build/dep changes, not a stub swap. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package for HoloScript project; name similarity to 'zod' is coincidental, not impersonation. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.0.11 | 2 / 3 | |
| 7.0.10 | 2 / 3 | |
| 7.0.9 | 2 / 3 | |
| 7.0.8 | 2 / 3 | |
| 7.0.7 | 2 / 3 | |
| 7.0.6 | 2 / 3 | |
| 7.0.5 | 2 / 3 | |
| 7.0.4 | 2 / 3 | |
| 7.0.3 | 2 / 3 | |
| 7.0.2 | 2 / 3 | |
| 7.0.1 | 2 / 3 | |
| 7.0.0 | 0 / 3 | |
| 6.0.3 | 0 / 3 | |
| 3.1.1 | 0 / 3 | |
| 2.1.0 | 0 / 3 |
v7.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
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: brianonbased.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
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: brianonbased.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
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: brianonbased.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
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: brianonbased.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
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: brianonbased.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
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: brianonbased.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
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: brianonbased.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
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: brianonbased.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.