@simpleview/cms-foundation
Provides helper types and components to assist when working with Granicus CMS Reactor.
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/routes/index.js | AI (source-diff): File is a standard esbuild bundle of pathe and other deps; no actual network+exec malware pattern present. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New export entry points (routes, vite) added with bundled deps explain the file count increase. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by new bundled entry points; consistent with package.json exports additions. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.0.34 | 1 / 7 | |
| 0.0.32 | 1 / 7 | |
| 0.0.31 | 1 / 7 | |
| 0.0.30 | 1 / 7 | |
| 0.0.29 | 1 / 7 | |
| 0.0.28 | 2 / 6 | |
| 0.0.27 | 1 / 7 | |
| 0.0.26 | 0 / 8 | |
| 0.0.25 | 0 / 8 | |
| 0.0.24 | 0 / 6 | |
| 0.0.23 | 0 / 6 | |
| 0.0.22 | 0 / 6 | |
| 0.0.21 | 0 / 6 | |
| 0.0.20 | 0 / 6 | |
| 0.0.18 | 0 / 6 | |
| 0.0.17 | 0 / 6 | |
| 0.0.16 | 0 / 6 | |
| 0.0.15 | 3 / 6 | |
| 0.0.14 | 2 / 6 | |
| 0.0.13 | 2 / 6 | |
| 0.0.12 | 2 / 6 | |
| 0.0.11 | 2 / 6 | |
| 0.0.10 | 2 / 6 | |
| 0.0.9 | 2 / 6 | |
| 0.0.8 | 2 / 6 | |
| 0.0.7 | 2 / 6 | |
| 0.0.6 | 2 / 6 | |
| 0.0.5 | 2 / 6 | |
| 0.0.4 | 2 / 6 | |
| 0.0.3 | 1 / 6 | |
| 0.0.2 | 1 / 5 | |
| 0.0.1 | 1 / 5 |
v0.0.34
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.