@sap-ux/adp-flp-config-sub-generator
Generator for adding FLP configuration to an Adaptation Project
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is SAP's open-source admin account; consistent with org-level governance for SAP/open-ux-tools. | ai | |
| provenance | publisher-changed | AI (provenance): SAP org migrated to GitHub Actions CI/CD publishing with SLSA attestation; stable pattern for this package going forward. | ai | |
| dependencies | unvetted-dep:@sap-ux/adp-tooling | AI (dependencies): Same SAP org scope; expected sibling dependency for this package family. | ai | |
| dependencies | unvetted-dep:@sap-ux/system-access | AI (dependencies): Same SAP org scope; expected sibling dependency for this package family. | ai | |
| dependencies | unvetted-dep:@sap-ux/feature-toggle | AI (dependencies): Same SAP org scope; expected sibling dependency for this package family. | ai | |
| dependencies | unvetted-dep:@sap-devx/yeoman-ui-types | AI (dependencies): SAP devx org scope; expected UI tooling dependency for this package family. | ai | |
| dependencies | unvetted-dep:@sap-ux/flp-config-inquirer | AI (dependencies): Same SAP org scope; expected sibling dependency for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Large SAP open-ux-tools monorepo; provenance not configured but repo URL and publisher track record are consistent. | ai | |
| dependencies | unvetted-dep:@sap-ux/axios-extension | AI (dependencies): Same SAP org scope; expected sibling dependency for this package family. | ai | |
| dependencies | unvetted-dep:@sap-ux/btp-utils | AI (dependencies): Same SAP org scope; expected sibling dependency for this package family. | ai | |
| phantom-deps | phantom-dep:@sap-ux/store | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a false positive for this monorepo package. | ai |
Versions (showing 51 of 268)
| Version | Deps | Published |
|---|---|---|
| 1.0.13 | 14 / 12 | |
| 1.0.12 | 14 / 12 | |
| 1.0.11 | 14 / 12 | |
| 1.0.10 | 14 / 12 | |
| 1.0.9 | 14 / 12 | |
| 1.0.8 | 14 / 12 | |
| 1.0.7 | 14 / 12 | |
| 1.0.6 | 14 / 12 | |
| 1.0.4 | 14 / 12 | |
| 1.0.3 | 14 / 12 | |
| 1.0.1 | 14 / 12 | |
| 1.0.0 | 14 / 12 | |
| 0.2.11 | 14 / 11 | |
| 0.2.10 | 14 / 11 | |
| 0.2.9 | 14 / 11 | |
| 0.2.7 | 14 / 11 | |
| 0.2.6 | 14 / 11 | |
| 0.2.5 | 14 / 11 | |
| 0.2.3 | 14 / 11 | |
| 0.2.2 | 14 / 11 | |
| 0.2.1 | 14 / 11 | |
| 0.1.245 | 14 / 11 | |
| 0.1.244 | 14 / 11 | |
| 0.1.243 | 14 / 11 | |
| 0.1.242 | 14 / 11 | |
| 0.1.241 | 14 / 11 | |
| 0.1.239 | 14 / 11 | |
| 0.1.238 | 14 / 11 | |
| 0.1.237 | 14 / 11 | |
| 0.1.236 | 14 / 11 | |
| 0.1.235 | 14 / 11 | |
| 0.1.234 | 14 / 11 | |
| 0.1.233 | 14 / 11 | |
| 0.1.232 | 14 / 11 | |
| 0.1.231 | 14 / 11 | |
| 0.1.230 | 14 / 11 | |
| 0.1.229 | 14 / 11 | |
| 0.1.228 | 14 / 11 | |
| 0.1.227 | 14 / 11 | |
| 0.1.226 | 14 / 11 | |
| 0.1.225 | 14 / 11 | |
| 0.1.224 | 14 / 11 | |
| 0.1.223 | 14 / 11 | |
| 0.1.222 | 14 / 11 | |
| 0.1.221 | 14 / 11 | |
| 0.1.220 | 14 / 11 | |
| 0.1.219 | 14 / 11 | |
| 0.1.218 | 14 / 11 | |
| 0.1.217 | 14 / 11 | |
| 0.1.216 | 14 / 11 | |
| 0.1.215 | 14 / 11 |
v1.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.11
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.10
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.9
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.7
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.6
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.245
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.244
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.243
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.242
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.241
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.233
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.232
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.231
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.230
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.229
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.228
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.227
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.226
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.225
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.224
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.223
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.222
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.221
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.220
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.216
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.215
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.