@treeseed/core
Treeseed integrated platform starter for Astro/Starlight web runtimes and Hono API runtimes.
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): process.env spread into env of a spawned npm install to disable install scripts; not exfiltrated anywhere. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are core Astro ecosystem packages; consistent with this Astro/Starlight framework's documented purpose. | ai | |
| dependencies | unvetted-dep:@astrojs/sitemap | AI (dependencies): Well-known Astro ecosystem package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@astrojs/starlight | AI (dependencies): Well-known Astro ecosystem package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@astrojs/cloudflare | AI (dependencies): Well-known Astro ecosystem package; no malware indicators. | ai | |
| phantom-deps | phantom-dep:katex | AI (phantom-deps): Math rendering dep referenced in config, not directly imported — expected for docs starter. | ai | |
| phantom-deps | phantom-dep:remark-gfm | AI (phantom-deps): Remark plugin referenced in config, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:remark-mdx | AI (phantom-deps): Remark plugin referenced in config, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:remark-stringify | AI (phantom-deps): Remark plugin referenced in config, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:remark-frontmatter | AI (phantom-deps): Remark plugin referenced in config, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:@astrojs/check | AI (phantom-deps): Astro type-checker referenced in scripts/config, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:remark-parse | AI (phantom-deps): Remark plugin referenced in config, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:wrangler | AI (phantom-deps): Framework starter; wrangler referenced in config/scripts, not imported directly — expected pattern. | ai | |
| phantom-deps | phantom-dep:vitest | AI (phantom-deps): Test runner referenced in vitest.config.ts, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): CSS framework referenced in config files, not directly imported — expected for Astro starter. | ai | |
| phantom-deps | phantom-dep:unified | AI (phantom-deps): Remark/unified pipeline dep referenced in config, not directly imported — expected pattern. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @treeseed/core is not a typosquat of 'cors'. The edit-distance match is on the unscoped portion only; the full name, repo, and purpose are clearly distinct. | ai |
Versions (showing 51 of 120)
| Version | Deps | Published |
|---|---|---|
| 0.12.36 | 27 / 2 | |
| 0.12.26 | 27 / 2 | |
| 0.12.25 | 27 / 2 | |
| 0.12.5 | 27 / 2 | |
| 0.11.0 | 26 / 1 | |
| 0.10.22 | 25 / 1 | |
| 0.10.21 | 25 / 1 | |
| 0.10.20 | 25 / 1 | |
| 0.10.19 | 25 / 1 | |
| 0.10.18 | 25 / 1 | |
| 0.10.17 | 25 / 1 | |
| 0.10.16 | 25 / 1 | |
| 0.10.15 | 25 / 1 | |
| 0.10.14 | 25 / 1 | |
| 0.10.13 | 25 / 1 | |
| 0.10.12 | 25 / 1 | |
| 0.10.11 | 25 / 1 | |
| 0.10.10 | 25 / 1 | |
| 0.10.9 | 25 / 1 | |
| 0.10.8 | 25 / 1 | |
| 0.10.7 | 25 / 1 | |
| 0.10.6 | 25 / 1 | |
| 0.10.5 | 25 / 1 | |
| 0.10.4 | 25 / 1 | |
| 0.10.3 | 25 / 1 | |
| 0.10.2 | 25 / 1 | |
| 0.10.1 | 25 / 1 | |
| 0.10.0 | 25 / 1 | |
| 0.9.4 | 25 / 1 | |
| 0.9.0 | 25 / 1 | |
| 0.8.19 | 25 / 1 | |
| 0.8.18 | 25 / 1 | |
| 0.8.17 | 25 / 1 | |
| 0.8.16 | 25 / 1 | |
| 0.8.15 | 25 / 1 | |
| 0.8.14 | 25 / 1 | |
| 0.8.13 | 25 / 1 | |
| 0.8.12 | 25 / 1 | |
| 0.8.11 | 25 / 1 | |
| 0.8.10 | 25 / 1 | |
| 0.8.9 | 25 / 1 | |
| 0.8.8 | 25 / 1 | |
| 0.8.7 | 25 / 1 | |
| 0.8.6 | 25 / 1 | |
| 0.8.5 | 25 / 1 | |
| 0.8.4 | 25 / 1 | |
| 0.8.3 | 24 / 1 | |
| 0.8.2 | 24 / 1 | |
| 0.8.1 | 24 / 1 | |
| 0.8.0 | 24 / 1 | |
| 0.7.0 | 24 / 1 |
v0.12.36
2 findingsThis version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/treeseed-ai/core/blob/c5d11ffdbd3a264c5884d2e66fe5942d6be9af2a/scripts/verify-driver.ts#L26 24 | const result = spawnSync('npm', ['install'], { 25 | cwd: process.cwd(), > 26 | env: { ...process.env, npm_config_ignore_scripts: 'true' }, 27 | stdio: 'inherit', 28 | });
v0.12.26
2 findingsThis version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/treeseed-ai/core/blob/25ea58c5fc4d2fb3dacd98b768e13777b29a1d46/scripts/verify-driver.ts#L26 24 | const result = spawnSync('npm', ['install'], { 25 | cwd: process.cwd(), > 26 | env: { ...process.env, npm_config_ignore_scripts: 'true' }, 27 | stdio: 'inherit', 28 | });
v0.12.25
2 findingsThis version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/treeseed-ai/core/blob/9dc2cd5969500359d001a1b3645b173a37531819/scripts/verify-driver.ts#L26 24 | const result = spawnSync('npm', ['install'], { 25 | cwd: process.cwd(), > 26 | env: { ...process.env, npm_config_ignore_scripts: 'true' }, 27 | stdio: 'inherit', 28 | });
v0.12.5
2 findingsThis version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/treeseed-ai/core/blob/fc5cda43cc0995771c94a1c9829259f5058a24b5/scripts/verify-driver.ts#L26 24 | const result = spawnSync('npm', ['install'], { 25 | cwd: process.cwd(), > 26 | env: { ...process.env, npm_config_ignore_scripts: 'true' }, 27 | stdio: 'inherit', 28 | });
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.