@nsshunt/stsvueutils
Vue 3 framework utilities and plugins
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:chalk | AI (phantom-deps): Direct dependency in Vue utility library; false positive. | ai | |
| phantom-deps | phantom-dep:pinia | AI (phantom-deps): Direct dependency in Vue 3 framework utilities; false positive. | ai | |
| phantom-deps | phantom-dep:js-cookie | AI (phantom-deps): Direct dependency in Vue utility library; false positive. | ai | |
| phantom-deps | phantom-dep:@nsshunt/stsobservability | AI (phantom-deps): Same-org scoped dependency; false positive. | ai |
Versions (showing 68 of 68)
| Version | Deps | Published |
|---|---|---|
| 2.0.102 | 3 / 14 | |
| 2.0.101 | 3 / 14 | |
| 2.0.100 | 3 / 14 | |
| 2.0.99 | 3 / 14 | |
| 2.0.98 | 3 / 14 | |
| 2.0.97 | 3 / 14 | |
| 2.0.96 | 3 / 14 | |
| 2.0.95 | 3 / 14 | |
| 2.0.94 | 3 / 14 | |
| 2.0.93 | 3 / 14 | |
| 2.0.92 | 3 / 14 | |
| 2.0.91 | 3 / 14 | |
| 2.0.90 | 3 / 14 | |
| 2.0.89 | 3 / 14 | |
| 2.0.88 | 3 / 14 | |
| 2.0.87 | 3 / 14 | |
| 2.0.86 | 3 / 14 | |
| 2.0.85 | 3 / 14 | |
| 2.0.84 | 6 / 14 | |
| 2.0.83 | 6 / 14 | |
| 2.0.82 | 6 / 14 | |
| 2.0.81 | 6 / 14 | |
| 2.0.80 | 6 / 14 | |
| 2.0.79 | 6 / 14 | |
| 2.0.78 | 6 / 14 | |
| 2.0.77 | 6 / 14 | |
| 2.0.76 | 6 / 14 | |
| 2.0.75 | 6 / 14 | |
| 2.0.74 | 6 / 14 | |
| 2.0.73 | 6 / 14 | |
| 2.0.72 | 6 / 14 | |
| 2.0.71 | 6 / 14 | |
| 2.0.70 | 6 / 14 | |
| 2.0.69 | 6 / 14 | |
| 2.0.68 | 6 / 14 | |
| 2.0.67 | 6 / 14 | |
| 2.0.66 | 6 / 14 | |
| 2.0.65 | 6 / 14 | |
| 2.0.64 | 6 / 14 | |
| 2.0.63 | 6 / 14 | |
| 2.0.62 | 6 / 14 | |
| 2.0.61 | 6 / 14 | |
| 2.0.60 | 6 / 14 | |
| 2.0.59 | 6 / 14 | |
| 2.0.58 | 6 / 14 | |
| 2.0.57 | 6 / 14 | |
| 2.0.56 | 6 / 14 | |
| 2.0.55 | 6 / 14 | |
| 2.0.54 | 6 / 14 | |
| 2.0.53 | 6 / 14 | |
| 2.0.52 | 6 / 14 | |
| 2.0.51 | 6 / 14 | |
| 2.0.50 | 6 / 14 | |
| 2.0.49 | 6 / 14 | |
| 2.0.48 | 6 / 14 | |
| 2.0.47 | 6 / 14 | |
| 2.0.46 | 6 / 14 | |
| 2.0.45 | 6 / 14 | |
| 2.0.44 | 6 / 14 | |
| 2.0.43 | 6 / 14 | |
| 2.0.42 | 6 / 14 | |
| 2.0.41 | 6 / 14 | |
| 2.0.40 | 6 / 14 | |
| 2.0.39 | 6 / 14 | |
| 2.0.38 | 6 / 14 | |
| 2.0.37 | 6 / 14 | |
| 2.0.36 | 7 / 19 | |
| 2.0.35 | 7 / 19 |
v2.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.