@or-sdk/flows
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Entire @or-sdk suite lacks descriptions/repo URLs; pattern is consistent across 559 versions, not a malice indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across @or-sdk packages; not indicative of malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across this SDK family; stable false positive for this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 2.7.5 | 5 / 2 | |
| 2.7.4 | 5 / 2 | |
| 2.7.3 | 5 / 2 | |
| 2.7.2 | 5 / 2 | |
| 2.7.1 | 5 / 2 | |
| 2.7.0 | 5 / 2 | |
| 2.6.0 | 5 / 2 | |
| 2.5.1 | 7 / 2 | |
| 2.5.0 | 7 / 2 | |
| 2.4.7 | 7 / 2 | |
| 2.4.6 | 7 / 2 | |
| 2.4.5 | 7 / 2 | |
| 2.4.4 | 7 / 2 | |
| 2.4.3 | 7 / 2 | |
| 2.4.2 | 7 / 2 | |
| 2.4.1 | 7 / 2 | |
| 2.4.0 | 7 / 2 | |
| 2.3.6 | 4 / 2 | |
| 2.3.5 | 4 / 2 | |
| 2.3.4 | 4 / 2 | |
| 2.3.3 | 4 / 2 | |
| 2.3.2 | 4 / 2 | |
| 2.3.1 | 4 / 2 | |
| 2.3.0 | 4 / 2 | |
| 2.2.12 | 4 / 2 | |
| 2.2.11 | 4 / 2 | |
| 2.2.10 | 4 / 2 | |
| 2.2.9 | 4 / 2 | |
| 2.2.8 | 4 / 2 | |
| 2.2.7 | 4 / 2 | |
| 2.2.6 | 4 / 2 | |
| 2.2.5 | 4 / 2 | |
| 2.2.4 | 4 / 2 | |
| 2.2.3 | 4 / 2 | |
| 2.2.2 | 4 / 2 |
v2.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.