@platforma-sdk/workflow-tengo
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established package with 241 versions; provenance absence is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:@milaboratories/software-pframes-conv | AI (phantom-deps): Platform binary dep referenced in config, not directly imported — stable pattern for this SDK package. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.software-ptabler | AI (phantom-deps): Platform binary dep referenced in config, not directly imported — stable pattern for this SDK package. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.software-ptexter | AI (phantom-deps): Platform binary dep referenced in config, not directly imported — stable pattern for this SDK package. | ai | |
| phantom-deps | phantom-dep:@platforma-open/milaboratories.software-small-binaries | AI (phantom-deps): Platform-specific binary package; declared but not directly imported is expected behavior. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 6.3.2 | 5 / 1 | |
| 6.3.1 | 5 / 1 | |
| 6.3.0 | 5 / 1 | |
| 6.2.0 | 5 / 1 | |
| 6.1.0 | 5 / 1 | |
| 6.0.0 | 5 / 1 | |
| 5.26.0 | 5 / 1 | |
| 5.25.0 | 5 / 1 | |
| 5.24.0 | 4 / 1 | |
| 5.23.0 | 4 / 1 | |
| 5.22.0 | 4 / 1 | |
| 5.21.0 | 4 / 1 | |
| 5.20.1 | 4 / 1 | |
| 5.20.0 | 4 / 1 | |
| 5.19.0 | 4 / 1 | |
| 5.18.0 | 4 / 1 | |
| 5.17.0 | 4 / 1 | |
| 5.16.0 | 4 / 1 | |
| 5.15.1 | 4 / 1 | |
| 5.15.0 | 4 / 1 | |
| 5.14.0 | 4 / 1 | |
| 5.13.3 | 4 / 1 | |
| 5.13.2 | 4 / 1 | |
| 5.13.1 | 4 / 1 | |
| 5.13.0 | 4 / 1 | |
| 5.12.1 | 4 / 1 | |
| 5.12.0 | 4 / 1 | |
| 5.8.1 | 4 / 1 | |
| 5.8.0 | 4 / 1 | |
| 5.7.3 | 4 / 1 | |
| 5.7.2 | 4 / 1 | |
| 5.7.1 | 4 / 1 | |
| 5.7.0 | 4 / 1 | |
| 5.6.6 | 4 / 1 | |
| 5.6.5 | 4 / 1 | |
| 5.6.4 | 4 / 1 | |
| 5.6.3 | 4 / 1 | |
| 5.6.2 | 4 / 1 | |
| 5.6.1 | 4 / 1 | |
| 5.6.0 | 4 / 1 | |
| 5.5.17 | 4 / 1 | |
| 5.5.16 | 4 / 1 | |
| 5.5.15 | 4 / 1 | |
| 5.5.14 | 4 / 1 | |
| 5.5.13 | 4 / 1 | |
| 5.5.12 | 4 / 1 | |
| 5.5.11 | 4 / 1 | |
| 5.5.10 | 4 / 1 | |
| 5.5.9 | 4 / 1 | |
| 5.5.8 | 4 / 1 | |
| 5.5.7 | 4 / 1 |
v6.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.