← Home

@stacksjs/ts-i18n

npm Repository Homepage

Fast, Bun-native TypeScript i18n loader with YAML/TS support and type generation.

7
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

chrisbreuerglenn123

Keywords

i18nbuntypescriptyamltranslationlocalization

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): stacksjs org consistently publishes initial versions at 0.0.0; not indicative of malice. ai
phantom-deps phantom-dep:yaml AI (phantom-deps): yaml is a declared runtime dep used via config files; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:bunfig AI (phantom-deps): bunfig is a declared runtime dep; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:tinyglobby AI (phantom-deps): tinyglobby is a declared runtime dep; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:@stacksjs/clapp AI (phantom-deps): Same-org dep declared in dependencies; phantom-dep heuristic false positive. ai

Versions (showing 7 of 7)

Version Deps Published
0.1.9 2 / 1
0.1.8 2 / 1
0.1.7 2 / 1
0.1.6 2 / 1
0.1.5 2 / 1
0.1.4 2 / 1
0.0.0 4 / 1

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

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.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

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.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.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.