@vertesia/common
Shared TypeScript types and utilities for the Vertesia platform. This package contains common type definitions, interfaces, and helper functions used across Vertesia client and server.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/vertesia-common.js | AI (source-diff): Minified rollup bundle output; devDeps include rollup-plugin-terser. Pattern is stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal package; missing metadata is consistent across all approved versions. | ai | |
| provenance | publisher-changed | AI (provenance): bstefanescu is an established publisher (7 approved packages) within the Vertesia org; transition appears legitimate. | ai |
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 2 / 7 | |
| 1.4.0 | 2 / 7 | |
| 1.3.0 | 2 / 8 | |
| 1.2.0 | 2 / 8 | |
| 1.1.0 | 2 / 8 | |
| 1.0.0 | 2 / 8 | |
| 0.82.4 | 3 / 9 | |
| 0.82.3 | 3 / 9 | |
| 0.82.2 | 3 / 9 | |
| 0.82.1 | 3 / 9 | |
| 0.82.0 | 3 / 9 | |
| 0.81.1 | 3 / 9 | |
| 0.81.0 | 3 / 9 | |
| 0.80.1 | 3 / 9 | |
| 0.80.0 | 3 / 9 | |
| 0.79.4 | 3 / 9 | |
| 0.79.3 | 3 / 9 | |
| 0.79.2 | 3 / 9 | |
| 0.79.1 | 3 / 9 | |
| 0.79.0 | 3 / 9 | |
| 0.78.0 | 3 / 9 | |
| 0.77.0 | 3 / 9 | |
| 0.76.0 | 3 / 9 | |
| 0.75.0 | 3 / 9 | |
| 0.74.0 | 3 / 9 | |
| 0.73.0 | 3 / 9 | |
| 0.72.0 | 3 / 9 | |
| 0.71.0 | 3 / 9 | |
| 0.70.0 | 3 / 9 | |
| 0.69.0 | 3 / 9 | |
| 0.68.0 | 3 / 9 | |
| 0.67.0 | 3 / 9 | |
| 0.66.0 | 3 / 9 | |
| 0.65.0 | 3 / 9 | |
| 0.64.0 | 3 / 9 | |
| 0.63.0 | 3 / 9 | |
| 0.62.0 | 3 / 9 | |
| 0.61.0 | 3 / 9 | |
| 0.60.0 | 3 / 9 | |
| 0.59.0 | 3 / 9 | |
| 0.58.0 | 3 / 9 | |
| 0.57.0 | 3 / 9 | |
| 0.56.0 | 3 / 9 | |
| 0.55.0 | 4 / 4 | |
| 0.54.0 | 4 / 4 | |
| 0.52.0 | 4 / 4 | |
| 0.51.0 | 4 / 4 | |
| 0.50.1 | 3 / 4 | |
| 0.50.0 | 3 / 4 | |
| 0.49.0 | 3 / 4 | |
| 0.48.0 | 3 / 4 | |
| 0.47.0 | 3 / 4 | |
| 0.46.0 | 3 / 4 | |
| 0.45.3 | 3 / 4 | |
| 0.45.2 | 3 / 4 | |
| 0.45.1 | 3 / 4 | |
| 0.45.0 | 3 / 4 | |
| 0.44.0 | 3 / 4 | |
| 0.43.0 | 3 / 4 | |
| 0.42.2 | 3 / 4 |
v1.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.