@sap-ux/fiori-generator-shared
Commonly used shared functionality and types to support the fiori generator.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:mem-fs-editor | AI (dependencies): mem-fs-editor is a standard Yeoman/generator ecosystem dependency; appropriate for this SAP Fiori generator package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): SAP internal tooling package; sparse README and no keywords are expected for this type of library. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual to GitHub Actions CI/CD with SLSA provenance; standard for SAP org packages. | ai | |
| phantom-deps | phantom-dep:mem-fs | AI (phantom-deps): mem-fs is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 100 of 255)
| Version | Deps | Published |
|---|---|---|
| 1.2.5 | 11 / 9 | |
| 1.2.3 | 11 / 9 | |
| 1.2.2 | 11 / 9 | |
| 1.2.1 | 11 / 9 | |
| 1.2.0 | 11 / 9 | |
| 1.1.0 | 11 / 9 | |
| 1.0.20 | 11 / 9 | |
| 1.0.19 | 11 / 9 | |
| 1.0.18 | 11 / 9 | |
| 1.0.17 | 11 / 9 | |
| 1.0.16 | 11 / 9 | |
| 1.0.15 | 11 / 9 | |
| 1.0.14 | 11 / 9 | |
| 1.0.13 | 11 / 9 | |
| 1.0.12 | 11 / 9 | |
| 1.0.11 | 11 / 9 | |
| 1.0.10 | 11 / 9 | |
| 1.0.9 | 11 / 9 | |
| 1.0.8 | 11 / 9 | |
| 1.0.7 | 11 / 9 | |
| 1.0.6 | 10 / 10 | |
| 1.0.5 | 10 / 10 | |
| 1.0.3 | 10 / 10 | |
| 1.0.2 | 10 / 10 | |
| 1.0.1 | 10 / 10 | |
| 1.0.0 | 10 / 10 | |
| 0.15.6 | 10 / 9 | |
| 0.15.4 | 10 / 9 | |
| 0.15.3 | 10 / 9 | |
| 0.15.2 | 10 / 9 | |
| 0.15.1 | 10 / 9 | |
| 0.14.1 | 10 / 9 | |
| 0.14.0 | 10 / 9 | |
| 0.13.105 | 10 / 9 | |
| 0.13.104 | 10 / 9 | |
| 0.13.103 | 10 / 9 | |
| 0.13.102 | 10 / 9 | |
| 0.13.101 | 10 / 9 | |
| 0.13.100 | 10 / 9 | |
| 0.13.99 | 10 / 9 | |
| 0.13.98 | 10 / 9 | |
| 0.13.97 | 10 / 9 | |
| 0.13.96 | 10 / 9 | |
| 0.13.95 | 10 / 9 | |
| 0.13.94 | 10 / 9 | |
| 0.13.93 | 10 / 9 | |
| 0.13.92 | 10 / 9 | |
| 0.13.91 | 10 / 9 | |
| 0.13.90 | 10 / 9 | |
| 0.13.89 | 10 / 9 | |
| 0.13.88 | 10 / 9 | |
| 0.13.87 | 10 / 9 | |
| 0.13.86 | 10 / 9 | |
| 0.13.85 | 10 / 9 | |
| 0.13.84 | 10 / 9 | |
| 0.13.83 | 10 / 9 | |
| 0.13.82 | 10 / 9 | |
| 0.13.81 | 10 / 9 | |
| 0.13.80 | 10 / 9 | |
| 0.13.79 | 10 / 9 | |
| 0.13.77 | 10 / 9 | |
| 0.13.76 | 10 / 9 | |
| 0.13.75 | 10 / 9 | |
| 0.13.74 | 10 / 9 | |
| 0.13.73 | 10 / 9 | |
| 0.13.71 | 10 / 9 | |
| 0.13.70 | 10 / 9 | |
| 0.13.69 | 10 / 9 | |
| 0.13.68 | 10 / 9 | |
| 0.13.67 | 10 / 9 | |
| 0.13.66 | 10 / 9 | |
| 0.13.65 | 10 / 9 | |
| 0.13.64 | 10 / 9 | |
| 0.13.63 | 10 / 9 | |
| 0.13.62 | 10 / 9 | |
| 0.13.61 | 10 / 9 | |
| 0.13.60 | 10 / 9 | |
| 0.13.59 | 10 / 9 | |
| 0.13.58 | 10 / 9 | |
| 0.13.57 | 10 / 9 | |
| 0.13.55 | 10 / 9 | |
| 0.13.54 | 10 / 9 | |
| 0.13.53 | 10 / 9 | |
| 0.13.52 | 10 / 9 | |
| 0.13.51 | 10 / 9 | |
| 0.13.50 | 10 / 9 | |
| 0.13.49 | 10 / 9 | |
| 0.13.48 | 10 / 9 | |
| 0.13.47 | 10 / 9 | |
| 0.13.46 | 10 / 8 | |
| 0.13.45 | 10 / 8 | |
| 0.13.44 | 10 / 8 | |
| 0.13.43 | 10 / 8 | |
| 0.13.42 | 10 / 8 | |
| 0.13.41 | 10 / 8 | |
| 0.13.39 | 10 / 8 | |
| 0.13.38 | 10 / 8 | |
| 0.13.37 | 10 / 8 | |
| 0.13.36 | 10 / 8 | |
| 0.13.35 | 10 / 8 |
v1.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.87
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinea) than the most recent previously approved version (kranthie.sap) on 2026-03-18, but devinea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.13.86
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinea) than the most recent previously approved version (kranthie.sap) on 2026-03-17, but devinea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.13.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.