@everymatrix/general-registration
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/general-registration/PlayerConsents-Duni8Aqx-dd7cf325.js | AI (source-diff): Same minified bundle in general-registration dist; consistent with package's established build pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/PlayerConsents-Duni8Aqx-dd7cf325.js | AI (source-diff): Same minified Svelte ESM bundle; consistent with package's established build pattern. | ai | |
| source-diff | obfuscated-file:dist/cjs/PlayerConsents-Duni8Aqx-1d0f4f21.js | AI (source-diff): Standard Vite/Svelte minified build output; readable helpers and pure annotations confirm legitimate bundler output. | ai | |
| source-diff | obfuscated-file:dist/general-registration/PlayerConsents-BtzEjirY-52f88049.js | AI (source-diff): Standard Rollup/Vite minified build output; not obfuscated, consistent with package's existing dist pattern. | ai | |
| source-diff | obfuscated-file:dist/cjs/PlayerConsents-BtzEjirY-0870c312.js | AI (source-diff): Standard Rollup/Vite minified build output; not obfuscated, consistent with package's existing dist pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/PlayerConsents-BtzEjirY-52f88049.js | AI (source-diff): Standard Rollup/Vite minified build output; not obfuscated, consistent with package's existing dist pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped org package with 549 versions; missing metadata is a stable pattern for this internal component library. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this internal org package; not a malware indicator here. | ai |
Versions (showing 100 of 435)
| Version | Deps | Published |
|---|---|---|
| 1.58.0 | 0 / 0 | |
| 1.57.0 | 0 / 0 | |
| 1.56.3 | 0 / 0 | |
| 1.56.2 | 0 / 0 | |
| 1.56.1 | 0 / 0 | |
| 1.56.0 | 0 / 0 | |
| 1.55.1 | 0 / 0 | |
| 1.55.0 | 0 / 0 | |
| 1.54.12 | 0 / 0 | |
| 1.54.11 | 0 / 0 | |
| 1.54.10 | 0 / 0 | |
| 1.54.9 | 2 / 0 | |
| 1.54.8 | 2 / 0 | |
| 1.54.6 | 2 / 0 | |
| 1.54.4 | 2 / 0 | |
| 1.54.3 | 2 / 0 | |
| 1.54.2 | 2 / 0 | |
| 1.53.99 | 2 / 0 | |
| 1.53.12 | 2 / 0 | |
| 1.47.2 | 1 / 0 | |
| 1.47.1 | 1 / 0 | |
| 1.47.0 | 1 / 0 | |
| 1.46.1 | 1 / 0 | |
| 1.46.0 | 1 / 0 | |
| 1.45.14 | 1 / 0 | |
| 1.45.13 | 1 / 0 | |
| 1.45.11 | 1 / 0 | |
| 1.45.10 | 1 / 0 | |
| 1.45.9 | 1 / 0 | |
| 1.45.8 | 1 / 0 | |
| 1.45.7 | 1 / 0 | |
| 1.45.5 | 1 / 0 | |
| 1.45.4 | 1 / 0 | |
| 1.45.3 | 1 / 0 | |
| 1.45.2 | 1 / 0 | |
| 1.45.0 | 1 / 0 | |
| 1.44.0 | 1 / 0 | |
| 1.43.4 | 1 / 0 | |
| 1.43.3 | 1 / 0 | |
| 1.43.2 | 1 / 0 | |
| 1.43.1 | 1 / 0 | |
| 1.43.0 | 1 / 0 | |
| 1.42.0 | 1 / 0 | |
| 1.41.0 | 1 / 0 | |
| 1.40.0 | 1 / 0 | |
| 1.39.3 | 1 / 0 | |
| 1.39.2 | 1 / 0 | |
| 1.39.1 | 1 / 0 | |
| 1.39.0 | 1 / 0 | |
| 1.38.0 | 1 / 0 | |
| 1.37.11 | 1 / 0 | |
| 1.37.10 | 1 / 0 | |
| 1.37.9 | 1 / 0 | |
| 1.37.8 | 1 / 0 | |
| 1.37.7 | 1 / 0 | |
| 1.37.6 | 1 / 0 | |
| 1.37.5 | 1 / 0 | |
| 1.37.4 | 1 / 0 | |
| 1.37.3 | 1 / 0 | |
| 1.37.2 | 1 / 0 | |
| 1.37.0 | 1 / 0 | |
| 1.36.1 | 1 / 0 | |
| 1.36.0 | 1 / 0 | |
| 1.35.0 | 1 / 0 | |
| 1.34.2 | 1 / 0 | |
| 1.34.0 | 1 / 0 | |
| 1.33.5 | 1 / 0 | |
| 1.33.4 | 1 / 0 | |
| 1.33.3 | 1 / 0 | |
| 1.33.2 | 1 / 0 | |
| 1.33.1 | 1 / 0 | |
| 1.33.0 | 1 / 0 | |
| 1.32.4 | 1 / 0 | |
| 1.31.2 | 1 / 0 | |
| 1.31.1 | 1 / 0 | |
| 1.31.0 | 1 / 0 | |
| 1.30.1 | 1 / 0 | |
| 1.30.0 | 1 / 0 | |
| 1.29.9 | 1 / 0 | |
| 1.29.8 | 1 / 0 | |
| 1.29.7 | 1 / 0 | |
| 1.29.6 | 1 / 0 | |
| 1.29.5 | 1 / 0 | |
| 1.29.4 | 1 / 0 | |
| 1.29.3 | 1 / 0 | |
| 1.29.1 | 1 / 0 | |
| 1.29.0 | 1 / 0 | |
| 1.28.8 | 1 / 0 | |
| 1.28.7 | 1 / 0 | |
| 1.28.4 | 1 / 0 | |
| 1.28.0 | 1 / 0 | |
| 1.27.10 | 1 / 0 | |
| 1.27.9 | 1 / 0 | |
| 1.27.8 | 1 / 0 | |
| 1.27.7 | 1 / 0 | |
| 1.27.6 | 1 / 0 | |
| 1.27.5 | 1 / 0 | |
| 1.27.4 | 1 / 0 | |
| 1.27.3 | 1 / 0 | |
| 1.27.2 | 1 / 0 |
v1.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.