@contrail/documents
Documents library for contrail platform
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Change reflects move to CI/CD-attested publishing, not account compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fractional-indexing is a small, well-known utility dep; benign addition. | ai | |
| provenance | missing-githead | AI (provenance): Publisher is a known maintainer; missing gitHead reflects CI environment change, not malicious activity. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers share the -vibeiq org suffix; consistent with internal team rotation, not external takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal paired with same-org additions; consistent with routine team handoff. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a well-known implicit runtime dep for TypeScript decorators; stable false positive for this package. | ai |
Versions (showing 100 of 117)
| Version | Deps | Published |
|---|---|---|
| 1.12.0 | 6 / 9 | |
| 1.11.0 | 5 / 9 | |
| 1.10.0 | 5 / 9 | |
| 1.9.0 | 5 / 9 | |
| 1.8.0 | 5 / 9 | |
| 1.7.0 | 5 / 9 | |
| 1.6.0 | 5 / 9 | |
| 1.5.6 | 5 / 9 | |
| 1.5.5 | 5 / 9 | |
| 1.5.4 | 5 / 9 | |
| 1.5.3 | 5 / 9 | |
| 1.5.2 | 5 / 9 | |
| 1.5.1 | 6 / 8 | |
| 1.5.0 | 6 / 8 | |
| 1.4.2 | 6 / 8 | |
| 1.4.0 | 6 / 8 | |
| 1.3.29 | 5 / 8 | |
| 1.3.27 | 5 / 8 | |
| 1.3.26 | 5 / 8 | |
| 1.3.25 | 5 / 8 | |
| 1.3.24 | 5 / 8 | |
| 1.3.21 | 5 / 8 | |
| 1.3.20 | 5 / 8 | |
| 1.3.19 | 5 / 8 | |
| 1.3.18 | 5 / 8 | |
| 1.3.17 | 5 / 8 | |
| 1.3.16 | 5 / 8 | |
| 1.3.15 | 5 / 8 | |
| 1.3.14 | 5 / 8 | |
| 1.3.13 | 5 / 8 | |
| 1.3.12 | 5 / 8 | |
| 1.3.11 | 5 / 8 | |
| 1.3.10 | 5 / 8 | |
| 1.3.9 | 5 / 8 | |
| 1.3.8 | 5 / 8 | |
| 1.3.7 | 5 / 8 | |
| 1.3.6 | 5 / 8 | |
| 1.3.5 | 5 / 8 | |
| 1.3.4 | 5 / 8 | |
| 1.3.3 | 5 / 8 | |
| 1.3.2 | 5 / 8 | |
| 1.3.0 | 5 / 8 | |
| 1.2.8 | 5 / 8 | |
| 1.2.7 | 5 / 8 | |
| 1.2.6 | 5 / 8 | |
| 1.2.5 | 5 / 8 | |
| 1.2.4 | 5 / 8 | |
| 1.2.3 | 5 / 8 | |
| 1.2.2 | 5 / 8 | |
| 1.2.1 | 5 / 8 | |
| 1.2.0 | 5 / 8 | |
| 1.1.25 | 5 / 8 | |
| 1.1.24 | 5 / 8 | |
| 1.1.23 | 5 / 8 | |
| 1.1.22 | 5 / 8 | |
| 1.1.21 | 5 / 8 | |
| 1.1.20 | 5 / 8 | |
| 1.1.19 | 5 / 8 | |
| 1.1.18 | 5 / 8 | |
| 1.1.17 | 5 / 8 | |
| 1.1.16 | 5 / 8 | |
| 1.1.15 | 5 / 8 | |
| 1.1.14 | 5 / 8 | |
| 1.1.13 | 5 / 8 | |
| 1.1.12 | 5 / 8 | |
| 1.1.11 | 5 / 8 | |
| 1.1.10 | 5 / 8 | |
| 1.1.9 | 5 / 8 | |
| 1.1.8 | 5 / 8 | |
| 1.1.7 | 5 / 8 | |
| 1.1.6 | 5 / 8 | |
| 1.1.5 | 5 / 8 | |
| 1.1.4 | 5 / 8 | |
| 1.1.3 | 5 / 8 | |
| 1.1.2 | 5 / 8 | |
| 1.1.1 | 5 / 8 | |
| 1.1.0 | 5 / 8 | |
| 1.0.123 | 5 / 8 | |
| 1.0.122 | 5 / 8 | |
| 1.0.121 | 5 / 8 | |
| 1.0.120 | 5 / 8 | |
| 1.0.119 | 5 / 8 | |
| 1.0.118 | 5 / 8 | |
| 1.0.117 | 5 / 8 | |
| 1.0.116 | 5 / 8 | |
| 1.0.115 | 5 / 8 | |
| 1.0.114 | 5 / 8 | |
| 1.0.113 | 5 / 8 | |
| 1.0.112 | 5 / 8 | |
| 1.0.111 | 5 / 8 | |
| 1.0.110 | 5 / 8 | |
| 1.0.109 | 5 / 8 | |
| 1.0.108 | 4 / 8 | |
| 1.0.107 | 4 / 8 | |
| 1.0.106 | 4 / 8 | |
| 1.0.105 | 4 / 8 | |
| 1.0.104 | 4 / 8 | |
| 1.0.103 | 4 / 8 | |
| 1.0.102 | 4 / 8 | |
| 1.0.101 | 4 / 8 |
v1.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.