← Home

@sap-ux/feature-toggle

npm Repository
21
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): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with SAP monorepo CI/CD migration. ai
maintainer-change maintainer-added AI (maintainer-change): sap-ospo-admin is SAP's OSS admin account; consistent with SAP org governance. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD migration is a known pattern for SAP monorepo packages; not indicative of takeover. ai

Versions (showing 21 of 21)

Version Deps Published
1.0.5 0 / 4
1.0.4 0 / 4
1.0.3 0 / 4
1.0.2 0 / 4
1.0.1 0 / 4
1.0.0 0 / 4
0.4.0 0 / 3
0.3.8 0 / 3
0.3.7 0 / 4
0.3.6 0 / 4
0.3.5 0 / 4
0.3.4 0 / 4
0.3.3 0 / 4
0.3.2 0 / 4
0.3.1 0 / 4
0.3.0 0 / 4
0.2.4 0 / 4
0.2.3 0 / 5
0.2.2 0 / 5
0.2.1 0 / 5
0.2.0 0 / 5

v1.0.5

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.

v1.0.4

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. Only ~12% of npm packages have provenance, so this is common but not ideal.