@techsee/techsee-media-service-client
TechSee media service client
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise package from a large monorepo; sparse README and no keywords are expected for private/scoped packages. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Preinstall runs lockfile-lint/audit-ci/npmPkgJsonLint with || true fallback; no network fetch or arbitrary code execution. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 50.197.0 | 7 / 53 | |
| 50.196.0 | 7 / 53 | |
| 50.195.0 | 7 / 53 | |
| 50.193.0 | 7 / 53 | |
| 50.191.0 | 7 / 53 | |
| 50.188.0 | 7 / 53 | |
| 50.186.0 | 7 / 53 | |
| 50.183.0 | 7 / 53 | |
| 50.182.0 | 7 / 53 | |
| 50.180.0 | 7 / 53 |
v50.197.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v50.195.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v50.193.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v50.191.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v50.188.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v50.186.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v50.183.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v50.182.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v50.180.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.