← Home

@sap-ux/i18n

npm Repository
22
Versions
—
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

tqueckkranthie.sapsap_extncrepossap-ospo-admindevinea

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): SAP migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable for this package going forward. ai
maintainer-change maintainer-added AI (maintainer-change): sap-ospo-admin is an SAP org admin account; consistent with organizational governance transition. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD migration is expected; SLSA provenance confirms legitimate publish pipeline. ai

Versions (showing 22 of 22)

Version Deps Published
1.0.2 3 / 7
1.0.1 3 / 7
1.0.0 3 / 7
0.4.0 3 / 6
0.3.11 3 / 6
0.3.10 3 / 6
0.3.9 3 / 6
0.3.7 3 / 6
0.3.6 3 / 6
0.3.5 3 / 6
0.3.4 3 / 6
0.3.3 3 / 6
0.3.2 3 / 6
0.3.1 3 / 6
0.3.0 3 / 6
0.2.3 3 / 6
0.2.2 3 / 6
0.2.1 3 / 6
0.2.0 3 / 6
0.1.1 3 / 6
0.1.0 3 / 6
0.0.7 3 / 6

v1.0.2

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.

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.7

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.