@jskit-ai/workspaces-web
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@jskit-ai/auth-web | AI (phantom-deps): Same-org scope dependency, likely used indirectly via exports. | ai | |
| provenance | missing-githead | AI (provenance): Metadata gap from established publisher, no behavioral change. | ai | |
| phantom-deps | phantom-dep:@jskit-ai/users-core | AI (phantom-deps): Same-org dep; may be transitively used or conditionally imported in this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of @jskit-ai scoped package family; sparse metadata is a style choice, not spam indicator. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 0.1.114 | 8 / 0 | |
| 0.1.112 | 8 / 0 | |
| 0.1.111 | 8 / 0 | |
| 0.1.110 | 8 / 0 | |
| 0.1.109 | 8 / 0 | |
| 0.1.108 | 8 / 0 | |
| 0.1.107 | 8 / 0 | |
| 0.1.106 | 8 / 0 | |
| 0.1.105 | 8 / 0 | |
| 0.1.104 | 8 / 0 | |
| 0.1.103 | 8 / 0 | |
| 0.1.102 | 8 / 0 | |
| 0.1.101 | 8 / 0 | |
| 0.1.100 | 8 / 0 | |
| 0.1.99 | 8 / 0 | |
| 0.1.98 | 8 / 0 | |
| 0.1.97 | 8 / 0 | |
| 0.1.96 | 8 / 0 | |
| 0.1.95 | 8 / 0 | |
| 0.1.94 | 8 / 0 | |
| 0.1.93 | 8 / 0 | |
| 0.1.92 | 8 / 0 | |
| 0.1.91 | 8 / 0 | |
| 0.1.90 | 8 / 0 | |
| 0.1.89 | 8 / 0 | |
| 0.1.88 | 8 / 0 | |
| 0.1.87 | 8 / 0 | |
| 0.1.86 | 8 / 0 | |
| 0.1.85 | 8 / 0 | |
| 0.1.84 | 8 / 0 | |
| 0.1.83 | 8 / 0 | |
| 0.1.82 | 7 / 0 | |
| 0.1.81 | 7 / 0 | |
| 0.1.80 | 7 / 0 | |
| 0.1.79 | 7 / 0 | |
| 0.1.78 | 7 / 0 | |
| 0.1.77 | 7 / 0 | |
| 0.1.75 | 7 / 0 | |
| 0.1.74 | 7 / 0 | |
| 0.1.73 | 7 / 0 | |
| 0.1.72 | 7 / 0 | |
| 0.1.71 | 7 / 0 | |
| 0.1.70 | 7 / 0 | |
| 0.1.69 | 7 / 0 | |
| 0.1.68 | 7 / 0 | |
| 0.1.67 | 7 / 0 | |
| 0.1.66 | 7 / 0 | |
| 0.1.65 | 7 / 0 | |
| 0.1.64 | 7 / 0 | |
| 0.1.63 | 7 / 0 | |
| 0.1.61 | 7 / 0 |
v0.1.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.85
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: mercmobily.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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: mercmobily.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.83
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: mercmobily.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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: mercmobily.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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: mercmobily.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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: mercmobily.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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: mercmobily.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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: mercmobily.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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: mercmobily.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.