@edsis/sdk
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Automated frequent-publish SDK generator; benign gitHead gap, not a lineage regression. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Consistent with automated generator publishing dozens of versions rapidly. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit Angular runtime dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Generated SDK package, sparse metadata expected, not spam. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 22.0.93 | 1 / 0 | |
| 22.0.91 | 1 / 0 | |
| 22.0.90 | 1 / 0 | |
| 22.0.89 | 1 / 0 | |
| 22.0.88 | 1 / 0 | |
| 22.0.87 | 1 / 0 | |
| 22.0.84 | 1 / 0 | |
| 22.0.82 | 1 / 0 | |
| 22.0.81 | 1 / 0 | |
| 22.0.80 | 1 / 0 | |
| 22.0.79 | 1 / 0 | |
| 22.0.78 | 1 / 0 | |
| 22.0.77 | 1 / 0 | |
| 22.0.75 | 1 / 0 | |
| 22.0.74 | 1 / 0 | |
| 22.0.73 | 1 / 0 | |
| 22.0.72 | 1 / 0 | |
| 22.0.71 | 1 / 0 | |
| 22.0.70 | 1 / 0 | |
| 22.0.69 | 1 / 0 | |
| 22.0.68 | 1 / 0 | |
| 22.0.67 | 1 / 0 | |
| 22.0.66 | 1 / 0 | |
| 22.0.65 | 1 / 0 | |
| 22.0.64 | 1 / 0 | |
| 22.0.63 | 1 / 0 | |
| 22.0.62 | 1 / 0 | |
| 22.0.60 | 1 / 0 | |
| 22.0.56 | 1 / 0 | |
| 22.0.55 | 1 / 0 | |
| 22.0.53 | 1 / 0 | |
| 22.0.46 | 1 / 0 | |
| 22.0.45 | 1 / 0 | |
| 22.0.44 | 1 / 0 | |
| 22.0.41 | 1 / 0 | |
| 22.0.40 | 1 / 0 | |
| 22.0.39 | 1 / 0 | |
| 22.0.38 | 1 / 0 | |
| 22.0.37 | 1 / 0 | |
| 22.0.36 | 1 / 0 | |
| 22.0.34 | 1 / 0 | |
| 22.0.33 | 1 / 0 | |
| 22.0.31 | 1 / 0 | |
| 22.0.30 | 1 / 0 | |
| 22.0.28 | 1 / 0 | |
| 22.0.27 | 1 / 0 | |
| 22.0.26 | 1 / 0 | |
| 22.0.25 | 1 / 0 | |
| 22.0.24 | 1 / 0 | |
| 22.0.23 | 1 / 0 | |
| 22.0.15 | 1 / 0 |
v22.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.90
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.89
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.88
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.87
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.84
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.82
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.81
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.80
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.79
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.78
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.77
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.75
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.74
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.73
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.72
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.71
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.70
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.69
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.68
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.67
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.66
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.65
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.64
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.63
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.62
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.60
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.56
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.55
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.53
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.46
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.45
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.44
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.41
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.40
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.39
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.38
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.37
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.36
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.34
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.33
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.