@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 — 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 |
|---|---|---|---|---|
| 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 |
v1.19.0
2 findingsScript: test -d ../../node_modules/.bin && ../../node_modules/.bin/lockfile-lint --path package-lock.json --config .lockfile-lintrc.json && ../../node_modules/.bin/audit-ci --config .audit-ci.json && ../../node_modules/.bin/npmPkgJsonLint . --configFile .npmpackagejsonlintrc.json || true
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
2 findingsScript: test -d ../../node_modules/.bin && ../../node_modules/.bin/lockfile-lint --path package-lock.json --config .lockfile-lintrc.json && ../../node_modules/.bin/audit-ci --config .audit-ci.json && ../../node_modules/.bin/npmPkgJsonLint . --configFile .npmpackagejsonlintrc.json || true
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
2 findingsScript: ../../node_modules/.bin/lockfile-lint --path package-lock.json --config .lockfile-lintrc.json && ../../node_modules/.bin/audit-ci --config .audit-ci.json && ../../node_modules/.bin/npmPkgJsonLint . --configFile .npmpackagejsonlintrc.json
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.