@syllst/glost
GLOST word-level annotation plugin for syllst
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped syllst monorepo package; 'glost' is a domain term, not a typo of 'glob'. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped syllst monorepo package; 'glost' is a domain term, not a typo of 'got'. | ai | |
| phantom-deps | phantom-dep:vfile | AI (phantom-deps): vfile is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.5.6 | 3 / 6 | |
| 0.5.5 | 4 / 4 | |
| 0.5.0 | 4 / 4 | |
| 0.4.2 | 4 / 4 | |
| 0.4.1 | 4 / 4 | |
| 0.4.0 | 4 / 4 | |
| 0.1.2 | 4 / 4 | |
| 0.1.1 | 4 / 4 | |
| 0.1.0 | 4 / 4 |
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.