@sap-ux/nodejs-utils
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 |
|---|---|---|---|---|
| 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 | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is consistent with SAP OSS governance; legitimate org-level maintainer addition. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.0.8 | 5 / 5 | |
| 1.0.7 | 5 / 5 | |
| 1.0.6 | 5 / 5 | |
| 1.0.5 | 5 / 5 | |
| 1.0.4 | 5 / 5 | |
| 1.0.3 | 5 / 5 | |
| 1.0.2 | 5 / 5 | |
| 1.0.1 | 5 / 5 | |
| 1.0.0 | 5 / 5 | |
| 0.3.2 | 5 / 4 | |
| 0.3.1 | 4 / 4 | |
| 0.3.0 | 4 / 4 | |
| 0.2.22 | 4 / 4 | |
| 0.2.21 | 4 / 4 | |
| 0.2.20 | 4 / 4 | |
| 0.2.19 | 4 / 4 | |
| 0.2.18 | 4 / 4 | |
| 0.2.17 | 4 / 4 | |
| 0.2.16 | 4 / 4 | |
| 0.2.15 | 4 / 4 | |
| 0.2.14 | 4 / 4 | |
| 0.2.13 | 4 / 4 | |
| 0.2.12 | 4 / 4 | |
| 0.2.11 | 4 / 4 | |
| 0.2.10 | 4 / 4 | |
| 0.2.9 | 4 / 4 | |
| 0.2.8 | 4 / 4 | |
| 0.2.7 | 4 / 4 | |
| 0.2.5 | 4 / 4 | |
| 0.2.4 | 4 / 4 | |
| 0.2.3 | 4 / 4 | |
| 0.2.2 | 4 / 4 | |
| 0.2.1 | 4 / 3 | |
| 0.2.0 | 4 / 3 | |
| 0.1.9 | 4 / 3 | |
| 0.1.8 | 4 / 4 | |
| 0.1.7 | 4 / 4 | |
| 0.1.6 | 4 / 4 | |
| 0.1.5 | 4 / 4 | |
| 0.1.4 | 4 / 4 | |
| 0.1.3 | 4 / 4 | |
| 0.1.2 | 4 / 4 | |
| 0.1.1 | 4 / 4 | |
| 0.1.0 | 4 / 4 | |
| 0.0.3 | 4 / 4 | |
| 0.0.2 | 4 / 4 | |
| 0.0.1 | 4 / 4 |
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.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.