@spectrum-css/search
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Normal Adobe org maintainer rotation, no compromise indicators. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with maintainer handoff within same org. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publish (532d) rules out takeover per analyzer's own logic. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo package with staggered release cadence, not malicious. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.2.0 | 0 / 4 | |
| 8.1.2 | 0 / 4 | |
| 8.1.1 | 0 / 4 | |
| 8.1.0 | 0 / 4 | |
| 8.0.1 | 0 / 8 | |
| 8.0.0 | 0 / 8 | |
| 3.0.2 | 0 / 6 |
v8.2.0
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-09-15. It has since remained available on npm for 305 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.2
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-04-09. It has since remained available on npm for 464 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-03-12. It has since remained available on npm for 492 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-02-12. It has since remained available on npm for 520 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-02-04. It has since remained available on npm for 528 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
2 findingsThis version was published by a different npm account (patrickfulton) than the most recent previously approved version (garthdb) on 2025-01-31. It has since remained available on npm for 532 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.