@techsee/client
Public package meant to use by techsee associates
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher has strong track record; no behavioral change accompanies the maintainer swap. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Preinstall runs only lint/audit tooling with || true fallback; no malicious behavior, stable pattern for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.33.0 | 1 / 16 | |
| 1.20.0 | 1 / 16 | |
| 1.19.0 | 1 / 15 | |
| 1.18.0 | 1 / 15 | |
| 1.16.0 | 1 / 15 | |
| 1.15.0 | 1 / 15 | |
| 1.12.0 | 1 / 14 | |
| 1.6.0 | 1 / 14 | |
| 1.4.0 | 1 / 5 |
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.