← Home

@fkui/tsconfig

npm Repository Homepage

Shared tsconfig.json presets for libraries and applications based on FKUI

53
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

extmartin.carlsson

Keywords

fkuitsconfig

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation from the official org repo; stable going forward. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer aligns with the org's CI/CD transition; consistent with legitimate project maintenance. ai

Versions (showing 53 of 53)

Version Deps Published
6.52.0 0 / 0
6.51.0 0 / 0
6.50.0 0 / 0
6.49.0 0 / 0
6.48.0 0 / 0
6.47.0 0 / 0
6.46.0 0 / 0
6.45.0 0 / 0
6.44.0 0 / 0
6.43.0 0 / 0
6.42.0 0 / 0
6.41.0 0 / 0
6.40.0 0 / 0
6.39.0 0 / 0
6.38.0 0 / 0
6.37.0 0 / 0
6.36.0 0 / 0
6.35.0 0 / 0
6.34.1 0 / 0
6.34.0 0 / 0
6.33.0 0 / 0
6.32.0 0 / 0
6.31.0 0 / 0
6.30.0 0 / 0
6.29.0 0 / 0
6.28.0 0 / 0
6.27.0 0 / 0
6.26.0 0 / 0
6.25.0 0 / 0
6.24.0 0 / 0
6.23.0 0 / 0
6.22.0 0 / 0
6.21.0 0 / 0
6.20.1 0 / 0
6.20.0 0 / 0
6.19.0 0 / 0
6.18.0 0 / 0
6.17.0 0 / 0
6.16.0 0 / 0
6.15.0 0 / 0
6.14.0 0 / 0
6.13.0 0 / 0
6.12.0 0 / 0
6.11.0 0 / 0
6.10.0 0 / 0
6.9.0 0 / 0
6.8.0 0 / 0
6.7.0 0 / 0
6.6.0 0 / 0
6.5.0 0 / 0
6.4.0 0 / 0
6.3.1 0 / 0
6.3.0 0 / 0

v6.52.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.6.0

1 finding
LOW No provenance attestation provenance

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

v6.5.0

1 finding
LOW No provenance attestation provenance

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

v6.4.0

1 finding
LOW No provenance attestation provenance

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

v6.3.1

1 finding
LOW No provenance attestation provenance

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

v6.3.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.