@nsshunt/stsauthclient
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): Consistent across all versions of this org's packages; no CI provenance configured org-wide. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is from the same nsshunt org with a clean track record; not an external supply-chain injection. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package; sparse metadata is consistent across the @nsshunt/* ecosystem, not indicative of spam/malware. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across @nsshunt/* org packages; not a malice indicator here. | ai |
Versions (showing 80 of 80)
| Version | Deps | Published |
|---|---|---|
| 1.0.88 | 11 / 9 | |
| 1.0.87 | 11 / 9 | |
| 1.0.86 | 11 / 9 | |
| 1.0.85 | 11 / 9 | |
| 1.0.84 | 11 / 9 | |
| 1.0.83 | 11 / 9 | |
| 1.0.82 | 11 / 9 | |
| 1.0.81 | 11 / 9 | |
| 1.0.80 | 11 / 9 | |
| 1.0.79 | 11 / 9 | |
| 1.0.77 | 11 / 9 | |
| 1.0.76 | 11 / 9 | |
| 1.0.75 | 11 / 9 | |
| 1.0.74 | 11 / 9 | |
| 1.0.73 | 11 / 9 | |
| 1.0.72 | 11 / 9 | |
| 1.0.71 | 11 / 9 | |
| 1.0.70 | 11 / 8 | |
| 1.0.69 | 11 / 8 | |
| 1.0.68 | 11 / 8 | |
| 1.0.67 | 11 / 8 | |
| 1.0.66 | 11 / 8 | |
| 1.0.65 | 11 / 8 | |
| 1.0.62 | 11 / 8 | |
| 1.0.61 | 11 / 8 | |
| 1.0.60 | 11 / 8 | |
| 1.0.59 | 11 / 8 | |
| 1.0.58 | 10 / 8 | |
| 1.0.57 | 10 / 8 | |
| 1.0.56 | 10 / 8 | |
| 1.0.55 | 10 / 8 | |
| 1.0.54 | 10 / 8 | |
| 1.0.53 | 10 / 8 | |
| 1.0.52 | 10 / 8 | |
| 1.0.51 | 10 / 8 | |
| 1.0.50 | 10 / 8 | |
| 1.0.49 | 10 / 8 | |
| 1.0.48 | 10 / 8 | |
| 1.0.47 | 10 / 8 | |
| 1.0.46 | 10 / 8 | |
| 1.0.45 | 10 / 8 | |
| 1.0.44 | 10 / 8 | |
| 1.0.43 | 10 / 8 | |
| 1.0.42 | 10 / 8 | |
| 1.0.41 | 10 / 8 | |
| 1.0.40 | 10 / 8 | |
| 1.0.39 | 10 / 8 | |
| 1.0.38 | 10 / 8 | |
| 1.0.37 | 10 / 8 | |
| 1.0.36 | 10 / 8 | |
| 1.0.35 | 10 / 8 | |
| 1.0.34 | 10 / 8 | |
| 1.0.33 | 10 / 8 | |
| 1.0.32 | 10 / 8 | |
| 1.0.31 | 10 / 8 | |
| 1.0.30 | 10 / 8 | |
| 1.0.29 | 10 / 8 | |
| 1.0.28 | 10 / 8 | |
| 1.0.27 | 10 / 8 | |
| 1.0.26 | 10 / 8 | |
| 1.0.25 | 10 / 8 | |
| 1.0.24 | 10 / 8 | |
| 1.0.23 | 10 / 11 | |
| 1.0.22 | 10 / 11 | |
| 1.0.21 | 10 / 11 | |
| 1.0.20 | 11 / 12 | |
| 1.0.19 | 11 / 12 | |
| 1.0.18 | 11 / 13 | |
| 1.0.17 | 11 / 13 | |
| 1.0.16 | 11 / 13 | |
| 1.0.15 | 11 / 13 | |
| 1.0.14 | 11 / 13 | |
| 1.0.13 | 11 / 13 | |
| 1.0.12 | 11 / 13 | |
| 1.0.11 | 11 / 13 | |
| 1.0.10 | 11 / 13 | |
| 1.0.9 | 11 / 13 | |
| 1.0.8 | 11 / 13 | |
| 1.0.7 | 11 / 13 | |
| 1.0.6 | 11 / 13 |
v1.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.