@omnia/fx-sp
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI publisher is a documented org practice for this established package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 29 approved packages; large org package with 6117 versions — dormancy likely reflects release cadence, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is a typings/re-export wrapper; empty index.js and sparse README are structural, not spam indicators. | ai |
Versions (showing 100 of 164)
| Version | Deps | Published |
|---|---|---|
| 7.11.18 | 2 / 0 | |
| 7.11.17 | 2 / 0 | |
| 7.11.16 | 2 / 0 | |
| 7.11.15 | 2 / 0 | |
| 7.11.14 | 2 / 0 | |
| 7.11.13 | 2 / 0 | |
| 7.11.12 | 2 / 0 | |
| 7.11.11 | 2 / 0 | |
| 7.11.10 | 2 / 0 | |
| 7.11.9 | 2 / 0 | |
| 7.11.8 | 2 / 0 | |
| 7.11.7 | 2 / 0 | |
| 7.11.6 | 2 / 0 | |
| 7.11.5 | 2 / 0 | |
| 7.11.4 | 2 / 0 | |
| 7.11.3 | 2 / 0 | |
| 7.11.2 | 2 / 0 | |
| 7.11.1 | 2 / 0 | |
| 7.9.43 | 2 / 0 | |
| 7.9.42 | 2 / 0 | |
| 7.9.41 | 2 / 0 | |
| 7.9.40 | 2 / 0 | |
| 7.9.39 | 2 / 0 | |
| 7.9.38 | 2 / 0 | |
| 7.9.37 | 2 / 0 | |
| 7.9.36 | 2 / 0 | |
| 7.9.35 | 2 / 0 | |
| 7.9.34 | 2 / 0 | |
| 7.9.30 | 2 / 0 | |
| 7.9.29 | 2 / 0 | |
| 7.9.28 | 2 / 0 | |
| 7.9.27 | 2 / 0 | |
| 7.9.26 | 2 / 0 | |
| 7.9.25 | 2 / 0 | |
| 7.9.24 | 2 / 0 | |
| 7.9.23 | 2 / 0 | |
| 7.9.22 | 2 / 0 | |
| 7.9.21 | 2 / 0 | |
| 7.9.20 | 2 / 0 | |
| 7.9.19 | 2 / 0 | |
| 7.9.18 | 2 / 0 | |
| 7.9.17 | 2 / 0 | |
| 7.9.16 | 2 / 0 | |
| 7.9.15 | 2 / 0 | |
| 7.9.14 | 2 / 0 | |
| 7.9.13 | 2 / 0 | |
| 7.9.12 | 2 / 0 | |
| 7.9.11 | 2 / 0 | |
| 7.9.10 | 2 / 0 | |
| 7.9.9 | 2 / 0 | |
| 7.9.7 | 2 / 0 | |
| 7.9.6 | 2 / 0 | |
| 7.9.5 | 2 / 0 | |
| 7.9.4 | 2 / 0 | |
| 7.9.3 | 2 / 0 | |
| 7.9.2 | 2 / 0 | |
| 7.9.1 | 2 / 0 | |
| 7.9.0 | 2 / 0 | |
| 7.8.16 | 2 / 0 | |
| 7.8.15 | 2 / 0 | |
| 7.8.14 | 2 / 0 | |
| 7.8.13 | 2 / 0 | |
| 7.8.12 | 2 / 0 | |
| 7.8.11 | 2 / 0 | |
| 7.8.10 | 2 / 0 | |
| 7.8.9 | 2 / 0 | |
| 7.8.8 | 2 / 0 | |
| 7.8.7 | 2 / 0 | |
| 7.8.6 | 2 / 0 | |
| 7.8.5 | 2 / 0 | |
| 7.8.4 | 2 / 0 | |
| 7.8.3 | 2 / 0 | |
| 7.8.2 | 2 / 0 | |
| 7.8.1 | 2 / 0 | |
| 7.8.0 | 2 / 0 | |
| 7.7.27 | 2 / 0 | |
| 7.7.26 | 2 / 0 | |
| 7.7.25 | 2 / 0 | |
| 7.7.24 | 2 / 0 | |
| 7.7.23 | 2 / 0 | |
| 7.7.22 | 2 / 0 | |
| 7.7.21 | 2 / 0 | |
| 7.7.20 | 2 / 0 | |
| 7.7.19 | 2 / 0 | |
| 7.7.18 | 2 / 0 | |
| 7.7.17 | 2 / 0 | |
| 7.7.16 | 2 / 0 | |
| 7.7.15 | 2 / 0 | |
| 7.7.14 | 2 / 0 | |
| 7.7.13 | 2 / 0 | |
| 7.7.12 | 2 / 0 | |
| 7.7.11 | 2 / 0 | |
| 7.7.10 | 2 / 0 | |
| 7.7.9 | 2 / 0 | |
| 7.7.8 | 2 / 0 | |
| 7.7.7 | 2 / 0 | |
| 7.7.6 | 2 / 0 | |
| 7.7.5 | 2 / 0 | |
| 7.7.4 | 2 / 0 | |
| 7.7.3 | 2 / 0 |
v7.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.