@nsshunt/stsobservability
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared dependency; phantom-dep heuristic is not a blocker per policy. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Declared dependency; phantom-dep heuristic is not a blocker per policy. | ai | |
| phantom-deps | phantom-dep:@msgpack/msgpack | AI (phantom-deps): Declared dependency; phantom-dep heuristic is not a blocker per policy. | ai | |
| phantom-deps | phantom-dep:timsort | AI (phantom-deps): Declared in dependencies; used via transitive imports and typed in devDeps. | ai | |
| phantom-deps | phantom-dep:percentile | AI (phantom-deps): Declared in dependencies; phantom-dep heuristic does not account for transitive usage. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 1.0.162 | 4 / 11 | |
| 1.0.161 | 4 / 11 | |
| 1.0.160 | 4 / 11 | |
| 1.0.159 | 4 / 11 | |
| 1.0.158 | 4 / 11 | |
| 1.0.157 | 4 / 11 | |
| 1.0.156 | 4 / 11 | |
| 1.0.155 | 4 / 11 | |
| 1.0.154 | 4 / 11 | |
| 1.0.153 | 4 / 11 | |
| 1.0.152 | 4 / 11 | |
| 1.0.151 | 5 / 12 | |
| 1.0.150 | 5 / 12 | |
| 1.0.149 | 5 / 12 | |
| 1.0.148 | 5 / 12 | |
| 1.0.147 | 5 / 13 | |
| 1.0.146 | 5 / 13 | |
| 1.0.144 | 5 / 13 | |
| 1.0.143 | 5 / 13 | |
| 1.0.142 | 5 / 13 | |
| 1.0.141 | 5 / 13 | |
| 1.0.140 | 12 / 12 | |
| 1.0.139 | 12 / 12 | |
| 1.0.138 | 12 / 12 | |
| 1.0.137 | 12 / 12 | |
| 1.0.136 | 12 / 12 | |
| 1.0.135 | 12 / 12 | |
| 1.0.134 | 12 / 12 | |
| 1.0.133 | 12 / 12 | |
| 1.0.132 | 12 / 12 | |
| 1.0.131 | 13 / 12 | |
| 1.0.130 | 13 / 12 | |
| 1.0.129 | 13 / 12 | |
| 1.0.128 | 13 / 12 | |
| 1.0.127 | 13 / 12 | |
| 1.0.126 | 13 / 12 | |
| 1.0.125 | 13 / 12 | |
| 1.0.124 | 13 / 12 | |
| 1.0.123 | 13 / 12 | |
| 1.0.122 | 13 / 12 | |
| 1.0.121 | 13 / 12 | |
| 1.0.120 | 13 / 12 | |
| 1.0.119 | 13 / 12 | |
| 1.0.118 | 13 / 12 | |
| 1.0.117 | 13 / 12 | |
| 1.0.116 | 13 / 12 | |
| 1.0.115 | 13 / 12 | |
| 1.0.114 | 13 / 12 | |
| 1.0.113 | 13 / 12 | |
| 1.0.112 | 13 / 12 | |
| 1.0.111 | 13 / 13 |
v1.0.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.142
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.141
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.