@natrave/facility-service-types
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): mateus_duarte confirmed as known maintainer by email match on prior approved versions; legitimate team change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New publisher was already a known maintainer; not a hostile addition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainers consistent with org restructuring, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by publish from a known maintainer with no code changes; low risk for this package. | ai | |
| phantom-deps | phantom-dep:@natrave/auth-service-types | AI (phantom-deps): Same-org type dependency; declared as runtime dep for type re-exports, stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.1.1 | 2 / 16 | |
| 0.0.9 | 2 / 16 | |
| 0.0.8 | 2 / 16 | |
| 0.0.7 | 2 / 16 | |
| 0.0.6 | 2 / 16 | |
| 0.0.5 | 2 / 16 | |
| 0.0.4 | 2 / 16 | |
| 0.0.3 | 1 / 16 | |
| 0.0.2 | 1 / 16 |
v0.1.1
3 findingsAll previous maintainers (na_trave, th38amorim, d-uartepereira) were replaced by new maintainers (mateus_duarte). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mateus_duarte) than the most recent previously approved version (na_trave) on 2026-06-05, but mateus_duarte is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.