← Home

@arkts/shared

npm Repository Homepage
8
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

guhuan

Keywords

arktssharedtypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:ohos-typescript AI (phantom-deps): Used via config, not direct import; stable false positive. ai
phantom-deps phantom-dep:vscode-uri AI (phantom-deps): Used via config, not direct import; stable false positive. ai
dependencies unvetted-dep:ohos-typescript AI (dependencies): Legitimate OpenHarmony TypeScript fork used by this ArkTS tooling package. ai
semgrep semgrep:dynamic-require AI (semgrep): Loads local configured resource path, not remote/fetched code. ai

Versions (showing 8 of 8)

Version Deps Published
1.3.9 5 / 2
1.0.11 5 / 2
1.0.8 5 / 2
1.0.7 3 / 2
1.0.5 2 / 1
1.0.4 2 / 1
1.0.3 2 / 1
1.0.0 2 / 0

v1.3.9

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.

v1.0.11

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.

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.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.