@jskit-ai/users-core
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 | no-provenance | AI (provenance): Common for org-scoped packages; stable across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped org package; sparse metadata is consistent across all 82 versions, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern for this private org package; not indicative of malicious intent. | ai |
Versions (showing 51 of 138)
| Version | Deps | Published |
|---|---|---|
| 0.1.147 | 9 / 0 | |
| 0.1.146 | 9 / 0 | |
| 0.1.145 | 9 / 0 | |
| 0.1.143 | 9 / 0 | |
| 0.1.142 | 9 / 0 | |
| 0.1.141 | 9 / 0 | |
| 0.1.140 | 9 / 0 | |
| 0.1.139 | 9 / 0 | |
| 0.1.138 | 9 / 0 | |
| 0.1.137 | 9 / 0 | |
| 0.1.136 | 9 / 0 | |
| 0.1.135 | 9 / 0 | |
| 0.1.134 | 9 / 0 | |
| 0.1.133 | 9 / 0 | |
| 0.1.132 | 9 / 0 | |
| 0.1.131 | 9 / 0 | |
| 0.1.130 | 9 / 0 | |
| 0.1.129 | 9 / 0 | |
| 0.1.128 | 9 / 0 | |
| 0.1.127 | 9 / 0 | |
| 0.1.126 | 9 / 0 | |
| 0.1.125 | 9 / 0 | |
| 0.1.124 | 9 / 0 | |
| 0.1.123 | 9 / 0 | |
| 0.1.122 | 9 / 0 | |
| 0.1.121 | 9 / 0 | |
| 0.1.120 | 9 / 0 | |
| 0.1.119 | 9 / 0 | |
| 0.1.118 | 9 / 0 | |
| 0.1.117 | 9 / 0 | |
| 0.1.116 | 9 / 0 | |
| 0.1.115 | 9 / 0 | |
| 0.1.114 | 9 / 0 | |
| 0.1.113 | 9 / 0 | |
| 0.1.112 | 9 / 0 | |
| 0.1.111 | 9 / 0 | |
| 0.1.110 | 9 / 0 | |
| 0.1.109 | 9 / 0 | |
| 0.1.108 | 9 / 0 | |
| 0.1.107 | 9 / 0 | |
| 0.1.106 | 9 / 0 | |
| 0.1.105 | 9 / 0 | |
| 0.1.104 | 9 / 0 | |
| 0.1.103 | 9 / 0 | |
| 0.1.102 | 9 / 0 | |
| 0.1.101 | 9 / 0 | |
| 0.1.100 | 9 / 0 | |
| 0.1.99 | 9 / 0 | |
| 0.1.98 | 9 / 0 | |
| 0.1.97 | 9 / 0 | |
| 0.1.96 | 9 / 0 |
v0.1.147
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.146
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.145
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.143
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.142
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.141
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.140
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.139
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.138
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.137
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.136
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.135
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.134
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.133
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.132
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.131
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.130
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.127
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.125
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.