@opengis/cms
cms
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): Established @opengis org package with 113 versions; sparse metadata is a style issue, not a spam/malware indicator. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): VueUse peer dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@opengis/admin | AI (phantom-deps): Same-org dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:pinia | AI (phantom-deps): Pinia is a Vue state-management peer dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): Referenced in config/build files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): Build-time CLI tool used in npm scripts, not imported directly; stable FP. | ai | |
| phantom-deps | phantom-dep:@opengis/v3-core | AI (phantom-deps): Same-org dep; phantom detection is a known FP for org-scoped component packages. | ai | |
| phantom-deps | phantom-dep:@opengis/v3-filter | AI (phantom-deps): Same-org dep; same rationale as @opengis/v3-core. | ai | |
| phantom-deps | phantom-dep:@vitejs/plugin-vue | AI (phantom-deps): Vite plugin used in vite.config, not directly imported in source; stable FP. | ai | |
| source-diff | obfuscated-file:dist/vs-form-reference-list-CB-Tv0TA.js | AI (source-diff): Standard Vite/Rollup minified bundle output; sample shows normal Vue component code, not malicious obfuscation. | ai | |
| phantom-deps | phantom-dep:vue-router | AI (phantom-deps): Config-referenced dep in a Vite/Vue project; stable false positive. | ai | |
| phantom-deps | phantom-dep:lucide-vue-next | AI (phantom-deps): Config-referenced dep in a Vue/Vite project; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue frontend framework declared as dep for build/config; phantom-dep heuristic fires on config-only references. | ai | |
| phantom-deps | phantom-dep:@opengis/core | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is unreliable for config-referenced deps. | ai | |
| phantom-deps | phantom-dep:@opengis/form | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is unreliable for config-referenced deps. | ai | |
| phantom-deps | phantom-dep:@opengis/filter | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is unreliable for config-referenced deps. | ai | |
| phantom-deps | phantom-dep:@opengis/richtext | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is unreliable for config-referenced deps. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Config-referenced dep in a Vue/Vite project; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vue-i18n | AI (phantom-deps): Config-referenced dep in a Vue/Vite project; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vueuse/head | AI (phantom-deps): Config-referenced dep in a Vue/Vite project; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vuedraggable | AI (phantom-deps): Config-referenced dep in a Vue/Vite project; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @opengis package; no intent to impersonate cors. Edit-distance match is coincidental. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decodes image data for sharp WebP conversion; not a malicious payload pattern. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @opengis package; no intent to impersonate qs. Edit-distance match is coincidental. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 0.1.17 | 0 / 24 | |
| 0.1.16 | 0 / 24 | |
| 0.1.15 | 0 / 24 | |
| 0.1.14 | 0 / 24 | |
| 0.1.13 | 0 / 24 | |
| 0.1.12 | 0 / 24 | |
| 0.1.8 | 0 / 24 | |
| 0.1.4 | 0 / 24 | |
| 0.1.3 | 0 / 24 | |
| 0.1.2 | 0 / 24 | |
| 0.1.1 | 0 / 24 | |
| 0.1.0 | 0 / 24 | |
| 0.0.99 | 0 / 24 | |
| 0.0.98 | 0 / 24 | |
| 0.0.97 | 0 / 24 | |
| 0.0.96 | 0 / 24 | |
| 0.0.95 | 0 / 24 | |
| 0.0.94 | 0 / 24 | |
| 0.0.93 | 0 / 24 | |
| 0.0.92 | 0 / 24 | |
| 0.0.91 | 0 / 24 | |
| 0.0.90 | 0 / 24 | |
| 0.0.89 | 0 / 24 | |
| 0.0.88 | 0 / 24 | |
| 0.0.87 | 0 / 24 | |
| 0.0.86 | 0 / 24 | |
| 0.0.85 | 0 / 24 | |
| 0.0.84 | 0 / 24 | |
| 0.0.83 | 0 / 24 | |
| 0.0.82 | 0 / 24 | |
| 0.0.81 | 0 / 24 | |
| 0.0.80 | 0 / 24 | |
| 0.0.79 | 0 / 24 | |
| 0.0.78 | 0 / 24 | |
| 0.0.77 | 0 / 24 | |
| 0.0.76 | 0 / 24 | |
| 0.0.75 | 0 / 24 | |
| 0.0.74 | 0 / 24 | |
| 0.0.73 | 0 / 24 | |
| 0.0.72 | 0 / 24 | |
| 0.0.71 | 0 / 24 | |
| 0.0.70 | 0 / 24 | |
| 0.0.69 | 0 / 24 | |
| 0.0.68 | 0 / 24 | |
| 0.0.67 | 0 / 24 | |
| 0.0.66 | 0 / 24 | |
| 0.0.65 | 0 / 24 | |
| 0.0.64 | 0 / 24 | |
| 0.0.63 | 0 / 24 | |
| 0.0.62 | 0 / 24 | |
| 0.0.61 | 0 / 24 |
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aponasko) than the most recent previously approved version (setebosu) on 2026-05-26, but aponasko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.