← Home

glost-core

npm Repository Homepage
2
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

fustilio

Keywords

glostglossed-syntax-treenlcstmultilinguallanguage-learninglinguisticssyntax-treeunist

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:glost-common AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic unreliable for TS packages with indirect imports. ai
phantom-deps phantom-dep:unist-util-map AI (phantom-deps): Likely re-exported or used indirectly in TS; stable false positive for this package. ai
phantom-deps phantom-dep:unist-util-find AI (phantom-deps): Likely re-exported or used indirectly in TS; stable false positive for this package. ai
phantom-deps phantom-dep:unist-util-filter AI (phantom-deps): Likely re-exported or used indirectly in TS; stable false positive for this package. ai
phantom-deps phantom-dep:unist-util-remove AI (phantom-deps): Likely re-exported or used indirectly in TS; stable false positive for this package. ai
phantom-deps phantom-dep:unist-util-select AI (phantom-deps): Likely re-exported or used indirectly in TS; stable false positive for this package. ai
phantom-deps phantom-dep:unist-util-flatmap AI (phantom-deps): Likely re-exported or used indirectly in TS; stable false positive for this package. ai
phantom-deps phantom-dep:unist-util-modify-children AI (phantom-deps): Likely re-exported or used indirectly in TS; stable false positive for this package. ai

Versions (showing 2 of 2)

Version Deps Published
0.6.2 11 / 3
0.5.0 11 / 3

v0.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.